You can view and set Entire Operations defaults, for example, for the following:
This document covers the following topics:
Default Setting (1) - Language, Format, User Application, Retention Periods, Escape Characters
Default Setting (2) - Schedule, Start Time, Symbols, JCL, SYSOUT
Default Setting (3) - Logging, Accounting, APIs, Symbol Table, Encoding
Default Setting (4) - Run Number for Activation, Symbol Function Results
This section covers the following topics:
Note:
Each Entire Operations Library has its own default settings. You
may copy defaults from other library defaults by using PF9
(Copy).
17-04-07 ***** Entire Operations ***** 10:16:01
Default Setting (1)
-------------------------------------------------------------------------------
Language Code ==> 1__ English Default Node ==> 12345 BATCH
Date Format ==> I
Calendar Display ==> 2
OpSys Specials ==> _ (mark) User ID Definition ==> A
User Applic. in Menu ==> _ (mark) File Password Prompting ==> E
Network Default Activation Escape ==> @
Network Default Submission Escape ==> $
Retention Periods Logon Screen obligatory ==> N
Active Networks ==> ___2 Days Stack 'RETURN' on Logoff ==> Y
Active Jobs ==> ___4 Days
Active Conditions ==> ___7 Days
Standard Log ==> ___7 Days
Long Term Log ==> _180 Days
Accounting Data ==> _180 Days
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Down OSpec Menu |
You can change any modifiable value by replacing the current value.
The DBID and FNR fields in the upper part of the screen are for your information only and cannot be modified, except the definition of the Alternate System File. The parameters in these fields are the dynamic startup settings from the Natural Parameter Module and are used for a (re)start of the Monitor from the System Administrator Services.
| Field | Meaning | ||||||
|---|---|---|---|---|---|---|---|
| Language Code |
|
||||||
| Date Format |
|
||||||
| Calendar Display |
|
||||||
| OpSys Specials | Mark this field with any character and press ENTER to open a selection window for operating system defaults. See the following sections: | ||||||
| User Applic. in Menu | Mark this field with any character and press ENTER to create a user application definition in a separate window. See User Application in Main Menu. | ||||||
| Default Node | Default Entire System Server node ID. This node is used for all internal calls to Entire System Server if no other node number is specified explicitly. | ||||||
| User ID Definition |
|
||||||
| File Password Prompting |
|
||||||
| Network Default Activation Escape | Global escape character to be
used as prefix for Natural code lines and symbols to be replaced at activation
time. Default is the dollar sign ($).
You can define specific escape characters for each operating system by marking Operating System Specials. |
||||||
|
Note: |
|||||||
| Network Default Submission Escape | Global escape character to
precede symbols that are to be replaced at submission time. You can define
specific escape characters for each operating system by marking Operating
System Specials. Default is the dollar sign ($).
The character recommended for BS2000 is the semi-colon (;), for z/VSE the number sign (#). |
||||||
|
Note: |
|||||||
| Logon Screen obligatory | If Y is specified
here, the Entire Operations Logon screen is always presented. This setting is
recommended, if an external security system like RACF is installed, since a
password must be entered.
|
||||||
| Stack 'RETURN' on Logoff | If Y is specified
here, an Entire Operations online session will be finished with the Natural
command RETURN. Otherwise, it is not finished. Only
with RETURN can control be given back to another
Natural application.
|
||||||
If T is specified
here, the Natural session will be terminated with the Entire Operations
session.
|
|||||||
| Retention Periods: | |||||||
| Active Networks | Maximum length of time Entire
Operations keeps active networks in the active database. If the network is not
completed within this time, a warning message is issued to a mailbox linked to
the network.
Default is 2 days. Note: |
||||||
| Active Jobs | Maximum length of time Entire
Operations keeps the active jobs in the active database.
This period must be longer than the Active Network retention period. Jobs will be deactivated after this this time, even if the active network is not completed. Default is 2 days. Note: |
||||||
| Active Conditions | Maximum length of time Entire
Operations keeps the active conditions in the active database. This retention period also applies to resource allocations
with
deallocation
mode K (keep until explicit release).
Default is 7 days. |
||||||
| Standard Log | Maximum length of time Entire
Operations keeps standard log data and mailbox entries (information messages).
Default is 7 days. |
||||||
| Long Term Log | Maximum length of time Entire
Operations keeps long term log data and mailbox entries (waiting for condition,
symbol prompting). Long term data are Network and Job activation times with run
numbers, as well as job accounting information.
Default is 180 days. |
||||||
| Accounting Data | The maximum time span, for which
Entire Operations will keep accounting data.
Default is the retention period for long-term logging. |
||||||
This function allows you to invoke a user-defined Natural application from the Entire Operations Main Menu.
If you mark the User Application in Menu field on the Default Setting (1) screen and press ENTER, the following screen appears:
04.11.08 *** Entire Operations *** 17:35:18
User Application in Main Menu
-------------------------------------------------------------------------------
Application ==> SYSMAIN_
Menu Text ==> sysmain___________________________________________
The application must be callable from the Entire Operations environment.
By default, the program MENU will be invoked.
The application must return to Entire Operations with the Natural command
RETURN.
Example: RELEASE STACK ; STACK TOP COMMAND 'RETURN'
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save |
- Fields: User Application in Main Menu
Field Meaning Application Enter the name of the Natural application. It must be accessible from the Entire Operations environment and a program MENU must exist.
The application must be defined in Natural Security and must pass back control with the Natural
RETURNcommand.See also the example on the screen.
Menu Text The text you enter here will appear on the Entire Operations Main Menu beneath the heading Applications on the right-hand side of the screen.
| PF Key | Name | Function |
|---|---|---|
| PF10 | OSpec | Opens a selection window for operation systems. See also Accessing Operating System Specific Default Settings. |
To display the second screen of the default setting facility
Press PF8 (Down) on the Default Setting (1) screen.
A Default Setting (2) screen similar to the example below appears:
04.11.08 ***** Entire Operations ***** 11:31:26
Owner REQUEST Default Setting (2)
-------------------------------------------------------------------------------
Extraction of Schedules ==> 2__ Days before Activation
Activation before Earliest Start ==> 30_ min.
Default Latest Start after Earliest Start ==> +24 hours
Default Deadline after Earliest Start ==> +48 hours
End of previous Production Date ==> 01:00:00
Subnetwork Activation Mode ==> A
SYSOUT Line Limit ==> _____________ Run Number Limit ==> 99999
Rewrite prompted Symbols to Master Symbol Table ==> N (Y/N)
Default for 'Use Time in Schedule' ==> Y (Y/N)
Copy SYSOUT File before passing it to NOM ==> Y (Y/N)
Generate Header in submitted JCL ==> Y (Y/N)
Log Symbol Values in submitted JCL ==> Y (Y/N)
Log the changes made to an active/pregen. JCL ==> Y (Y/N)
Symbol Prompting during JCL Regeneration ==> N (Y/N)
Automatic cleanup for new day / monitor start ==> Y (Y/N) at ==> ________
Symbol table obligatory ==> N
Keep predefined job time frames ==> N (Y/N)
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Up Menu |
| Field | Meaning | ||
|---|---|---|---|
| Extraction of Schedules | The current network schedules are extracted once a day to prepare scheduled network activation. The extraction can be done several days in advance to permit earlier symbol prompting, etc. Enter the number of days. Default: 1 day (=current day). | ||
| Activation before Earliest Start | The activation creates an executable copy of the Job Network definition. This parameter allows you to activate the Network before the earliest time the Network is actually started. Default: 0 minutes. | ||
| Default latest Start after Earliest Start | This parameter applies if no explicit latest start time was specified on the job level. The time (in hours) specified here is added to the (computed) earliest start time. Default: 24 hours. | ||
| Default Deadline after Earliest Start | This parameter applies if no explicit deadline time was specified on the job level. The time (in hours) specified here is added to the (computed) earliest start time. Default: 48 hours. | ||
| End of previous Production Date | Time at which previous production
day ends logically. This time influences the following:
|
||
| Subnetwork Activation Mode | A
(or blank)
|
At activation time of the caller.
|
|
S |
At submission time of the caller. | ||
| See the section Time of Activation of a Subnetwork in the User's Guide for more information. | |||
| SYSOUT Line Limit | Determines
the line limit for SYSOUT.
If the SYSOUT of a job exceeds the line limit set, the lines are truncated after the line number specified in this field. This affects the following SYSOUT functions:
|
||
| Default: 0 (no limit) | |||
z/OS, JES2: The value is divided
by 1000 and inserted with a /*LINES command. If the division
result is 0, the value is set to 1.
|
|||
| Run Number Limit | The maximum run number which can be assigned to a network or job activation. The maximum must not exceed 99999. | ||
| Default: If 0 is specified, the limit will be 99999. | |||
| Rewrite prompted Symbols to Master Symbol Table | If you enter Y here,
prompted symbols are updated in the master symbol table, in addition to the
currently active symbol table. This keeps the last prompted value for the next
prompting.
|
||
| Default for Use Time in Schedule | Enter Y to use the
time frames of the schedule definition.
|
||
Enter N to use the
start time entered on this screen. Network and job time frames are not
honoured.
|
|||
| Copy SYSOUT File before passing it to NOM | This flag applies to BS2000 only. | ||
N |
The original SYSOUT file is passed to the
Entire Output Management
API.
Note: |
||
Y |
The SYSOUT file is copied physically and the copy will be passed to the Entire Output Management API. This doubles the necessary disk storage for SYSOUT files created by Entire Operations. (NOM: Entire Output Management) (Default). | ||
| Generate Header in submitted JCL | Enter Y to generate
header.
|
||
Enter N not to
generate header.
|
|||
| Log Symbol Values in submitted JCL | Enter Y to log
symbol values.
|
||
Enter N not to log
values.
|
|||
| Log the changes made to an active / pregenerated JCL | Enter Y to activate
the active JCL modification change logging. If this field is set to
Y, and if active or pregenerated JCL is modified, the changes are
written to the Entire Operations log. You may then mark this message, to see
the extended log, which contains the modifications to the active JCL. With this
option on, the Editor buffer pool space may have to be increased.
Enter |
||
| Symbol Prompting during JCL Regeneration | N |
No symbol prompting during JCL regeneration (default). | |
Y |
Symbols will be prompted again during JCL regeneration. | ||
| Automatic cleanup for new day / monitor start | N
|
No automatic cleanup of the active database and log data is performed. | |
Y |
Automatic cleanup of the active database and
log data is performed.
The interval between two subsequent automatic cleanups is at least one hour. This is the default. |
||
D |
Same as Y, but automatic cleanup
will not be performed, if a cleanup (automatic or manual) was already performed
on the same day.
|
||
| at | Enter the time to perform daily automatic cleanup. | ||
|
Note: |
|||
| Symbol table obligatory | ' ',N |
No symbol table definition required. | |
A |
Symbol table required for all networks. | ||
S |
Symbol table required for subnetworks only. | ||
|
You can force the definition of symbol tables with this setting. Note:
It is not performed for unchanged network definitions. To check the existence of symbol table definitions globally, use the batch utility CHNWST-P described in the section Entire Operations Utilities in the User's Guide. |
|||
| Keep predefined job time frames | N |
Use calling job's time frame for subnetwork jobs (default). | |
Y
|
Keep predefined job time frames. | ||
To display the third screen of the default setting facility
Press PF8 (Down) on the Default Setting (2) screen.
A Default Setting (3) screen similar to the example below appears:
03.01.14 ***** Entire Operations ***** 14:04:59
Default Setting (3)
-------------------------------------------------------------------------------
Logging and Accounting Settings
Log Logon/Logoff to nodes ==> N (Y/N)
Log API usage ==> N (Y/N)
Collect z/OS step accounting data ==> Y (Y/N)
Deactivation Settings
Confirm activation cancelling ==> N (Y/N)
Jobs to be deactivated at once ==> 2000_
NOM API Settings
NOM API retry limit ==> 3___
Pass empty files to NOM ==> N (Y/N)
Submit symbol/function recalculation at resubmit ==> Y (Y/N)
Symbol table activation mode ==> X
Encoding ==> T_______
Max. number of versions for networks or symbol tables ==> _______
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Up Menu |
| Field | Meaning | |
|---|---|---|
| Log Logon/Logoff to Nodes | If Y is specified
here, all logons and logoffs to and from Entire System Server nodes (by users
and monitor tasks) will be logged. Be aware of the overhead in the log file.
|
|
| Log API Usage | If Y is specified
here, some API executions will be logged. The API return code is contained. Be
aware of the overhead in the log file.
|
|
| Collect z/OS step accounting data | Y
|
Accounting data for steps will be collected additionally for z/OS
jobs.
Be aware of the overhead in the accounting data file. |
N |
Accounting data for steps will not be collected (Default). |
|
| Confirm activation cancelling | Y
|
Use confirm dialog, if future activations are cancelled
(Default).
See also Canceling an Active Job in the section Active Job Networks in the User's Guide. |
N |
No confirm dialog, if future activations are cancelled. | |
| Jobs to be deactivated at once | Maximum number of active jobs to be deactivated in one monitor cycle. | |
| Default: 50 | ||
| NOM API retry limit | Maximum number of attempts for passing a file to Entire Output Management (NOM). | |
| Default: 1000 | ||
| Pass empty files to NOM | Y |
Empty files will be passed to NOM. |
N |
Empty files will not be passed to NOM. | |
|
Note: |
||
| Submit symbol/function recalculation at resubmit | Active Submit Symbol/Function
Recalculation at Job Resubmission.
This setting determines the handling of submit symbol and function values during resubmit with submission symbol replacement. If If |
|
| Symbol table activation mode | X |
After schedule extraction. Symbol prompting can be used for scheduled networks (Default). |
A |
During the network activation. No symbol prompting is possible. | |
| Encoding | T |
Use trigraphs in active JCL and in JCL and
SYSOUT logging (applies for UNIX and Windows JCL only). For information on
trigraph
encoding, see the relevant section in the User's
Guide.
Default: blank (no encoding) |
8 |
Applies to JCL on UNIX only.
If the file is UTF-8 encoded, convert UTF-8 characters to HTML
format in the active JCL. In this case, you must not use the ampersand
( |
|
| Maximum number of versions for networks or symbol tables | The maximum number of versions
that might be defined for a network or symbol table.
This limit is checked during addition or cloning of versions. 0 = no restriction |
|
To display the fourth screen of the default setting facility
Press PF8 (Down) on the Default Setting (3) screen.
A Default Setting (4) screen similar to the example below appears:
17-09-14 ***** Entire Operations ***** 16:04:07
Default Setting (4)
-------------------------------------------------------------------------------
Activation Settings
Activation: Allow run number setting ==> Y (Y/N)
Symbol Functions
Write results of MM and MV to active symbol table ==> Y (Y/N)
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Up Menu |
| Field | Meaning | |
|---|---|---|
| Activation: Allow run number setting | Possible settings: | |
Y |
Allows users to request their preferred run number during network or job activation. See also the field Preferred Run Number described in the sections Fields: Network Activation (Network Maintenance) and Fields: Job Activation in the User's Guide. | |
N |
Users are not allowed to request a run number (default). | |
| Write results of MM and MV to active symbol table | Y |
The values returned for the symbol functions
MM
and MV
are written to the active symbol table. Subsequent symbol function executions
with the same parameters will use these values.
See also in the section Functions for Symbol Replacement in the User's Guide. |
N |
The values returned for the symbol functions
MM
and MV
are not written to the active symbol table (default).
|
|
To define operating system specific defaults
Mark the field OpSys Specials on the Default Setting (1) screen and press ENTER.
A selection window similar to the example below opens:
16.04.16 ***** Entire Operations ***** 10:27:28
Default Setting (1)
-------------------------------------------------------------------------------
Language Code ==> 1__ English Default Node ==> 146__ N0146
Date Format ==> G
Calendar Display ==> 1
OpSys Specials ==> x (mark) User ID Definition ==> A
User Applic. in Menu ==> _ (mark) File Password Prompting ==> N
Network Default Activation Escape ==> @
+----------------------------------------+ n Escape ==> $
Retention Periods | | ligatory ==> Y
Active Network | Please select the Operating System | n Logoff ==> Y
Active Job | |
Active Condition | _ BS2000 |
Standard Lo | _ z/OS |
Long Term Lo | _ z/VSE |
Accounting Dat | _ UNIX |
| _ Windows |
Command => _________ | | _______
+----------------------------------------+
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Down OSpec Menu |
Mark the appropriate operating system and press ENTER.
A screen appears with parameters for the operating system selected.
The following sections explain how to continue:
If you marked z/OS or z/VSE, see Defaults for z/OS and z/VSE.
If you marked BS2000, see Defaults for BS2000.
If you marked UNIX, see Defaults for UNIX.
Some specials for UNIX nodes can be defined on the Operating System Server (Node) Table screen (see also Special Definitions for a Node (UNIX and Windows).
If you marked Windows, see Defaults for Windows.
This section provides instructions for setting BS2000 defaults.
You can set the defaults for BS2000 on two screens:
Defaults for BS2000 (1) for general settings and
Defaults for BS2000 (2) for BS2000 message
codes that force a job not OK by default.
To set defaults for BS2000
Select BS2000 from the selection window on the Default Setting (1) screen.
A Defaults for BS2000 (1) screen similar the example below appears:
17-06-06 ***** Entire Operations ***** 11:31:07
Owner EXAMPLE Defaults for BS2000 (1)
------------------------------------------------------------------------------
End-of-Job Checking
Highest Severity Code accepted as ok ==> 0000
SYSOUT Handling
These values will be used as defaults for new job definitions:
Make the SYSOUT Collection File shareable ==> N (Y/N)
Append the SYSLST File(s) to the SYSOUT File ==> N (Y/N)
Monitor Job Variables
Remove internal Monitor Job Variables after End-of-Job Handling ==> Y (Y/N)
Escapes: Activation ==> @ Submission ==> "
Note: Modifications become effective at the next monitor startup.
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Down Menu |
This is the first BS2000-specific screen in a series of two. The fields available on this screen are explained in Fields: Defaults for BS2000 (1).
PF8 (Down) to open the second screen Defaults for BS2000 (2) containing a table for BS2000-specific message codes:
17-06-06 ***** Entire Operations ***** 11:36:48
Owner EXAMPLE Defaults for BS2000 (2)
------------------------------------------------------------------------------
BS2000 Message Codes, which force 'job not ok' by default:
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
_______ _______ _______ _______ _______
If you want to restore the default settings, please use PF4.
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Resto Save Up Menu |
For more information, see BS2000 Default Message Codes - Defaults for BS2000 (2).
This section covers the following topics:
The BS2000-specific fields on the Defaults for BS2000 (1) screen are explained in the following table.
Note:
New default settings become effective after the next Monitor
startup and are then used as defaults for new job definitions.
| Field | Meaning |
|---|---|
| End-of-Job Checking: | |
| Highest Severity Code accepted as ok | This value is the maximum allowed severity code for messages
matching the default message code table. If a message is defined without a
severity code, a match always means job not OK.
|
| SYSOUT Handling: | |
| Make the SYSOUT Collection File shareable | Entire Operations creates its own SYSOUT Collection
File for each BS2000 job running under Entire Operations control.
Enter Y if the Entire Operations Monitor should make these files
shareable; enter N if not.
|
| Append the SYSLST File(s) to the SYSOUT File | Enter Y if the SYSLST files created by a job
should be appended to the Entire Operations SYSOUT Collection
File; enter N if not.
|
| Monitor Job Variables: | |
| Remove internal Monitor Job Variables | Enter Y to remove internal Monitor job
variables immediately after End-of-Job checking. This creates fewer catalog
entries. Enter N to remove variables during standard job
deactivation.
Note: |
| Escapes: | |
| Activation | Activation escape character. This escape character is prefix
for Natural code lines and symbols to be replaced at activation time.
Note: |
| Submission | Submission escape character. This escape character is prefix
for symbols to be replaced at submission time.
Note: |
The table on the Defaults for BS2000 (2)
screen contains BS2000 message codes
that force a job not ok by default.
If one of the BS2000 message codes listed in this table appears in any
BS2000 job SYSOUT, a job is treated as not ok without any special
definition at the job level.
The BS2000 message codes listed in the following section are in effect after the installation of Entire Operations. You can restore the default set of message codes supplied with Entire Operations at any time by using PF4 (Resto).
Changes to the message codes are propagated to a running monitor immediately.
Notes:
not ok when the message code table is modified.
| Message Code | Message Text |
|---|---|
| IDA0N45 | Dump desired?
Reply (Y =user/area dump); Y, System = system dump; N = no). |
| IDA0N47 | Dump prohibited by /MODIFY-TEST-OPTIONS command. |
| IDA0N48 | Task/system settings prohibit dump. |
| IDA0N51 | Program interrupt at location '(&00)'. |
| IDA0N56 | Current system dump suppressed (duplicate). |
| EXC0733 | Unrecoverable termination error: task with TSN '(&00)' pended. Continue system run and take dump after shutdown. |
| EXC0734 | (Message not defined.) |
| EXC0735 | (Message not defined.) |
| EXC0736 | Abnormal task termination. Error code '(&00)': / Help-MSG (&00). |
| EXC0737 | (Message not defined.) |
| EXC0738 | (Message not defined.) |
| EXC0772 | (Message not defined.) |
| CMD0005 | Operation name in input string not recognizable or missing. |
| CMD0205 | Error in preceding command or program and procedure step termination: commands will be ignored until /SET-JOB-STEP or /LOGOFF or /EXIT-JOB is recognized. |
| JVS04A1 | Syntax error in JV command. Correct command. |
| DMS05A9 | Second file name in command for COPY invalid or does not exist. Correct command. |
| DMS0936 | (Message not defined.) |
| BLS0520 | Access error on program library.
PLAM-AMCB error code '(&00)' and system error code '(&01)' In system mode /HELP-MSG PLA (&00). |
| SSM2052 |
Procedure file '(&00)' cannot be opened. DMS error code '(&01)'. Command terminated. DMS error: /HELP-MSG-INFORMATION DMS(&01). |
| NRTT201 | NRTT201 TASK TERMINATION DUE TO /(&00)
COMMAND
The task termination was caused by a /CANCEL-JOB resp. /CANCEL or a /SHUTDOWN command. |
| CMD0186 | CMD0186 OPERATION NAME '(&00)' UNKNOWN. |
This section provides instructions for setting z/OS and z/VSE defaults.
To set defaults for z/OS or z/VSE
Select z/OS or z/VSE from the selection window on the Default Setting (1) screen.
For z/OS, a Defaults for z/OS screen similar the example below appears:
23/08/16 ***** Entire Operations ***** 15:51:44
Owner EXAMPLE Defaults for z/OS
-------------------------------------------------------------------------------
End-of-Job Checking
These values apply, if nothing is specified for the End-of-Job Checking:
Highest Condition Code accepted as ok ==> C 0009
= highest Severity Code (see field help)
Highest User Code accepted as ok ==> U ____
IEF201I 'Terminated because of condition codes' accepted as ok ==> N
End-of-Job Actions
Spool Class to be set after Job Completion ==> ________
Job Card
These values will be inserted into the job card, if missing:
MSGCLASS ==> ________ MSGLEVEL ==> ________
Escapes: Activation ==> @ Submission ==> $
Note: Modifications become effective at the next monitor startup.
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Menu |
For z/VSE, a Defaults for z/VSE screen similar the example below appears:
24/08/16 ***** Entire Operations ***** 12:11:06
Owner EXAMPLE Defaults for z/VSE
-------------------------------------------------------------------------------
End-of-Job Checking
These values apply, if nothing is specified for the End-of-Job Checking:
Highest Condition Code accepted as ok ==> C 0009
= highest Severity Code (see field help)
Highest User Code accepted as ok ==> U ____
End-of-Job Actions
Spool Class to be set after Job Completion ==> ________
JCL Location VSE
Default Member Type ==> J_______
Escapes: Activation ==> @ Submission ==> #
Note: Modifications become effective at the next monitor startup.
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Menu |
The fields available on the screens are explained in Fields: Defaults for z/OS and z/VSE.
The z/OS-specific and z/VSE-specific fields for default settings on the Defaults for z/OS and Defaults for z/VSE screen are explained in the following table.
Note:
New default settings become effective after the next Monitor
startup and are then used as defaults for new job definitions.
| Field | Meaning |
|---|---|
| End-of-Job Checking: | |
| The values specified with the following three fields are used for checking completed jobs if no definition has been made at the job level: | |
| Highest Condition Code
(= highest Severity Code) |
The value entered here is used for default checks of all step
results for which no dedicated check was defined. If such a step result is
higher than the value defined here, the job is treated as not ok.
This value is the maximum allowed severity code for messages
matching the Global Message Code
Table. If a message is defined there without a severity
code, a match always means |
| Highest User Code accepted as ok | Corresponds to Highest Condition Code but checks for user-defined codes only. |
| IEF201I 'Terminated because of condition codes' accepted as ok | Applies to z/OS only.
If
does not cause the job to be set to All other implicit or explicit End-of-Job checks are not affected by this setting. This is a system-wide setting. For more information, see the section End-of-Job Checking and Actions in the User's Guide. The default is |
| End-of-Job Actions: | |
| Spool Class to be set after Job Completion | You can specify that the spool class of a job is to be
modified after completion. This applies to all jobs.
Notes:
When you enter a valid spool class in this field, Entire Output Management knows exactly where to find all information necessary for the output files to be processed. If you leave this field blank, the job output class remains unchanged. For more information, see End-of-Job Checking and Actions in the User's Guide. |
| Job Card: | |
| MSGCLASS | Applies to z/OS only.
You can complete or modify the job card for any job by adding values for MSGCLASS and MSGLEVEL here. The values specified here are inserted if not already on the job card. |
| MSGLEVEL | |
| JCL Location VSE: | |
| Default Member Type | Applies to z/VSE only.
The default member type is inserted into JCL definitions if nothing else is specified. |
| Escapes: | |
| Activation | Activation escape character. This escape character is prefix
for Natural code lines and symbols to be replaced at activation time.
Note: |
| Submission | Submission escape character. This escape character is prefix
for symbols to be replaced at submission time.
Note: |
This section provides instructions for setting UNIX defaults.
To set defaults for UNIX
Select UNIX from the selection window on the Default Setting (1) screen.
A Defaults for UNIX screen similar the example below appears:
25/08/16 ***** Entire Operations ***** 18:12:45
Owner EXAMPLE Defaults for UNIX
-------------------------------------------------------------------------------
End-of-Job Checking
Highest Exit Code accepted as ok ==> 0_________
Escapes: Activation ==> @ Submission ==> ^
Note: Modifications become effective at the next monitor startup.
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Menu |
The fields available on the screen are explained in Fields: Defaults for UNIX.
The UNIX-specific fields on the Defaults for UNIX screen are explained in the following table.
Note:
New default settings become effective after the next Monitor
startup and are then used as defaults for new job definitions.
| Field | Meaning |
|---|---|
| End-of-Job Checking: | |
| Highest Exit Code accepted as ok | The value entered here is the maximum exit code which is
accepted as ok.
|
| Escapes: | |
| Activation | Activation escape character. This escape character is prefix
for Natural code lines and symbols to be replaced at activation time.
Note: |
| Submission | Submission escape character. This escape character is prefix
for symbols to be replaced at submission time.
Note: |
This section provides instructions for setting Windows defaults.
To set defaults for Windows
Select Windows from the selection window on the Default Setting (1) screen.
A Defaults for Windows screen similar the example below appears:
25/08/16 ***** Entire Operations ***** 18:13:46
Owner EXAMPLE Defaults for Windows
-------------------------------------------------------------------------------
End-of-Job Checking
Highest Exit Code accepted as ok ==> 0_________
Escapes: Activation ==> ( Submission ==> (
Note: Modifications become effective at the next monitor startup.
Command => ____________________________________________________________
Enter-PF1---PF2---PF3---PF4---PF5---PF6---PF7---PF8---PF9---PF10--PF11--PF12---
Help End Save Menu |
The fields available on the screen are explained in Fields: Defaults for Windows.
The Windows-specific fields on the Defaults for Windows screen are explained in the following table.
Note:
New default settings become effective after the next Monitor
startup and are then used as defaults for new job definitions.
| Field | Meaning |
|---|---|
| End-of-Job Checking: | |
| Highest Exit Code accepted as ok | The value entered here is the maximum exit code which is
accepted as ok.
|
| Escapes: | |
| Activation | Activation escape character. This escape character is prefix
for Natural code lines and symbols to be replaced at activation time.
Note: |
| Submission | Submission escape character. This
escape character is prefix for symbols to be replaced at submission time.
Note: |