Entire Operations Defaults

You can view and set Entire Operations defaults, for example, for the following:

Features specific to the character user interface of Entire Operations;
Entire Operations system file and log files;
Defaults for z/OS and z/VSE, BS2000, UNIX and Windows;
User definitions;
Display options (language, calendar, date);
Interface settings and escape characters;
Retention periods and start/end dates for networks and jobs;
Logging, activation and APIs;
Scheduling, symbols, JCL and SYSOUT.

This document covers the following topics:

Accessing Default Settings for Entire Operations
Defaults: System/Log Files
Defaults for Operating System Specials
Defaults for Time Ranges
Defaults for Network Options
Defaults for Other Settings
Defaults for Character Interface Settings
Defaults for BS2000
Defaults for z/OS and z/VSE
Defaults for UNIX
Defaults for Windows

Accessing Default Settings for Entire Operations

To access the default settings for Entire Operations

In the object workspace, select Administration.
Open the context menu and select Entire Operations Defaults.

An Entire Operations Defaults window with an open System/Log files page similar to the example below opens:

Each tabbed page represents a set of default settings, you can specify for your environment.

The tabbed pages are explained in the following section.

Defaults: System/Log Files

The system and log files shown on the System/Log files page of the Entire Operations Defaults window are explained in Entire Operations Files.

The fields in the Logging settings section of the page are described in the following table:

Field	Description
Log logon/logoff to node	If this check box is selected, 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 symbol values in submitted JCL	Possible check-box settings:
	`checked`	Log symbol values.
	`unchecked`	Do not log values.
Log the changes made to an active/pregen. JCL	Possible check-box settings:
	`checked`	Activate the active JCL modification change logging. If this check box is selected 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.
	`unchecked`	Disable this feature. This is the default.
Log API Usage	If this check box is selected, some API executions will be logged. The API return code is contained. Be aware of the overhead in the log file.

Defaults for Operating System Specials

graphics/defaults_os.png

The fields provided on the Operating System Specials page of the Entire Operations Defaults window depend on the operating system selected as shown in the example of z/OS above. The fields are explained in the following operating system specific sections:

Defaults for z/OS and z/VSE
Defaults for BS2000
Defaults for UNIX
Defaults for Windows

Defaults for Time Ranges

graphics/defaults_time.png

The fields on the Time Ranges page of the Entire Operations Defaults window are described in the following table:

Field/Section	Description
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: Unfinished active jobs are deactivated after the Active Jobs retention period in any case.
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: The retention period for an active job is calculated backwards from the real start time of the job, if available. Otherwise, it is calculated backwards from the activation time of the job.
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 Keep until explicit release (`K`). 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.
Extraction of schedules before activation	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: Condition references: The reference PDA for input condition references the production date, not the current calendar date. Symbol replacement: The predefined symbol `P-DATE` provides the production date in the format YYYYMMDD. See also Predefined Symbols and Date and Time Formats in the User's Guide.
Automatic cleanup	Possible selection options:
	No automatic cleanup for new day If selected, no automatic cleanup of the active database and log data is performed.
	Automatic cleanup for new day / monitor start at If selected, 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. You can enter the time to perform daily automatic cleanup. Note: To avoid an overflow of the active database, the cleanup must be triggered at least once a day.
	once per day If selected, automatic cleanup will not be performed if a cleanup (automatic or manual) was already performed on the same day.
Append to Export File	Opens the Export Objects window to export the default settings currently defined. Proceed as described in Exporting Objects in the Import/Export Functions documentation.

Defaults for Network Options

graphics/defaults_network.png

The fields on the Network Options page of the Entire Operations Defaults window are described in the following table:

Field	Description
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 on the Operating System Specials page. Note: Dynamic JCL might become invalid if this escape character is changed.
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 on the Operating System Specials page. Default is the dollar sign ($). The character recommended for BS2000 is the semi-colon (;), and for z/VSE the number sign (#). Note: Dynamic JCL might become invalid if this escape character is changed.
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: Extended SYSOUT logging is truncated. SYSOUT browsing of a file or spool data set is truncated and ends with a warning message similar to the following: `===== EOR4123 - SYSOUT line limit 1000 reached =====` SYSOUT is truncated if copied from UNIX or Windows to the mainframe (for example, BS2000). SYSOUT is truncated if passed from UNIX or Windows to Entire Output Management (NOM), depending on the Entire System Server version installed at your site (see the relevant announcement in the current Entire Operations Release Notes). Log messages are written for the above cases.
	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 is 99999.
Subnetwork activation mode	Possible selection options:
	At activation time	At activation time of the caller. This is the default.
	During the network activation	At submission time of the caller.
	See also the section Time of Activation of a Subnetwork in the User's Guide.
Symbol table obligatory	Possible selection options:
	No symbol table required	No symbol table definition required.
	Required for all networks	Symbol table required for all networks.
	Required for subnetworks only	Symbol table required for subnetworks only.
	You can force the definition of symbol tables with this setting. Note: The existence check is performed: during a network activation if a network is added if a network is modified 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.
Max. number of versions per network or symbol table	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
Allow setting of preferred run number during activation	If this check box is selected, users are allowed 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 (Job Maintenance) in the User's Guide. This check box is not selected by default.
Append to Export File	Opens the Export Objects window to export the default settings currently defined. Proceed as described in Exporting Objects in the Import/Export Functions documentation.

Defaults for Other Settings

graphics/defaults_others.png

The fields on the Others page of the Entire Operations Defaults window are described in the following table:

Field/Section	Description
Date format	Date format to be used for date fields. For explanations of the possible selection options, see Date and Time Formats in the User's Guide.
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	Possible selection options:
	All JCL or submit user IDs may be defined This is the default.
	User must have logged on successfully to a node First, the user must have logged on successfully to a node. Then a JCL or submit user ID may be defined.
	A logon is always required for: User ID `TSOS` on BS2000 nodes User ID `root` on UNIX nodes
File password prompting	Possible selection options:
	Do not prompt for password Do not prompt for a password. Use the defined password, if necessary. This is the default.
	Always prompt for a file password before editing If a file is password-protected, always prompt for a file password before editing.
Symbol table activation mode	Possible selection options:
	After schedule extraction Symbol prompting can be used for scheduled networks. This is the default.
	During the network activation No symbol prompting is possible.
Time frames	Possible selection options:
	Default for 'Use time in schedule' The calling job's time frame for subnetwork jobs is used. This is the default.
	Keep predefined job time frames The predefined job time frames are kept.
Rewrite prompted symbols to master symbol table	If this check box is selected, 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.
Copy SYSOUT file before passing it to NOM	Applies to BS2000 only. Possible check-box settings:
	`checked`	The SYSOUT file is copied physically and the copy will be passed to the Entire Output Management (NOM) API. This doubles the necessary disk storage for SYSOUT files created by Entire Operations. This is the default.
	`unchecked`	The original SYSOUT file is passed to the Entire Output Management (NOM) API.
	Note: If the copying of SYSOUT files for NOM is switched off, SYSOUT files may get lost or overwritten, if creating job is resubmitted, or restarted for a recovery, etc.
Generate header in submitted JCL	Possible check-box settings:
	`checked`	Generate header.
	`unchecked`	Do not generate header.
Symbol prompting during JCL regeneration	Possible check-box settings:
	`checked`	Symbols will be prompted again during JCL regeneration.
	`unchecked`	No symbol prompting during JCL regeneration. This is the default.
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. Possible check-box settings:
	`checked`	Active submit symbols and functions will be deleted and activated (calculated) anew. This is the default.
	`unchecked`	Resubmission will be performed with the same submit symbol and function values.
Write results of MM and MV to active symbol table	Possible check box settings:
	`checked`	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.
	`unchecked`	The values returned for the symbol functions `MM` and `MV` are not written to the active symbol table (default).
Deactivation Settings	Confirm activation cancelling Possible check box settings:
	`checked`	The confirm dialog is used if future activations are cancelled. This is the default.
	`unchecked`	No confirm dialog is used if future activations are cancelled.
	Jobs to be deactivated at once The maximum number of active jobs to be deactivated in one monitor cycle. Default is 50.
NOM API Settings	NOM API retry limit The maximum number of attempts for passing a file to Entire Output Management (NOM). Default is 1000.
	Pass empty files to NOM Possible check box settings:
	`checked`	Empty files are passed to Entire Output Management (NOM).
	`unchecked`	Empty files are not passed to Entire Output Management (NOM). This is the default.
	Note: A log message is written in any case.
Encoding
	Applies for UNIX and Windows JCL only. Use trigraphs in JCL and SYSOUT logging Possible check box settings:
	`checked`	Use trigraphs in active JCL and in JCL and SYSOUT logging. For information on trigraph encoding, see the relevant section in the User's Guide.
	`unchecked`	Encoding is not used. This is the default.
	Applies to UNIX JCL only.
	Convert UTF-8 characters to HTML format in the active JCL Possible check box settings:
	`checked`	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 (`&`) as the submit escape character.
	`unchecked`	UTF-8 characters are not converted. This is the default.
Append to Export File	Opens the Export Objects window to export the default settings currently defined. Proceed as described in Exporting Objects in the Import/Export Functions documentation.

Defaults for Character Interface Settings

graphics/defaults_intface.png

The fields on the Character interface settings page of the Entire Operations Defaults window are described in the following table.

These settings only affect the application screens of the Entire Operations character user interface.

Field/Section	Description
Language	Determines the Entire Operations default language code. Possible selection options: English German
User application in menu	Integrates a user-defined application into the Entire Operations Main Menu.
	Application	The name of the required application.
	Menu text	The name to be used in the Main Menu.
	See also Integration of Other Applications in the Concepts and Facilities documentation.
Calendar display	Select Support highlighting to enable highlighting in calendar displays provided that your terminal supports highlighting.
Session control	Stack 'RETURN' on logoff Possible check box settings:
	`checked`	Terminates an Entire Operations online session with the Natural command `RETURN`. Only with `RETURN` can control be given back to another Natural application.
	`unchecked`	Terminates a Natural session with the Entire Operations session.
	Logon screen obligatory Possible check box settings:
	`checked`	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.
	`unchecked`	The Entire Operations logon screen is not presented.
Append to Export File	Opens the Export Objects window to export the default settings currently defined. Proceed as described in Exporting Objects in the Import/Export Functions documentation.

Defaults for BS2000

This section describes the fields provided for BS2000 default settings.

This section covers the following topics:

Fields: Defaults for BS2000
BS2000 Default Message Codes

Fields: Defaults for BS2000

The BS2000-specific fields on the Operations System Specials page of the Entire Operations Defaults window 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. Select this check box if the Entire Operations Monitor should make these files shareable; do not select this check box if not.
Append the SYSLST File(s) to the SYSOUT File	Select this check box if the SYSLST files created by a job should be appended to the Entire Operations SYSOUT Collection File; do not select this check box if not.
Monitor Job Variables:
Remove internal Monitor Job Variables after End-of-Job handling	Select this check box to remove internal Monitor job variables immediately after End-of-Job checking. This creates fewer catalog entries. Do not select this check box to remove variables during standard job deactivation. Note: This setting affects only Monitor job variables which were internally created by the Entire Operations Monitor.
Escapes:
Activation	Activation escape character. This escape character is prefix for Natural code lines and symbols to be replaced at activation time. Note: Existing Dynamic JCL might become invalid after changing this escape character.
Submission	Submission escape character. This escape character is prefix for symbols to be replaced at submission time. Note: Existing Dynamic JCL might become invalid after changing this escape character.
Message codes, which force 'job not ok' by default	See BS2000 Default Message Codes.

BS2000 Default Message Codes

The table on the below Message codes, which force 'job not ok' by default 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 Restore Defaults function.

Changes to the message codes are propagated to a running monitor immediately.

Notes:

Consider that faulty jobs may no longer be set to the status not ok when the message code table is modified.
The message code table can be completely empty. None of the mentioned BS2000 message codes would be checked by default in this case.

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.

Defaults for z/OS and z/VSE

This section describes the fields provided for z/OS and z/VSE default settings.

Fields: Defaults for z/OS and z/VSE

The z/OS-specific and z/VSE-specific fields for default settings on the Operations System Specials page of the Entire Operations Defaults window 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 `job not ok`.
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 this option is selected, the occurrence of the message `EF201I ... - JOB TERMINATED BECAUSE OF CONDITION CODES` does not cause the job to be set to `not ok` automatically. 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. This option is not selected be default.
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: Node-specific definitions override this default. Job-specific definitions override all others. 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
Collect z/OS step accounting data:
`checked`	Applies to z/OS only. If this check box is selected, accounting data for steps will be collected additionally for z/OS jobs. Be aware of the overhead in the accounting data file.
`unchecked`	If this check box is not selected, accounting data for steps will not be collected (default).
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: Existing dynamic JCL might become invalid after changing this escape character.
Submission	Submission escape character. This escape character is prefix for symbols to be replaced at submission time. Note: Existing dynamic JCL might become invalid after changing this escape character.

Defaults for UNIX

This section describes the fields provided for UNIX default settings.

Fields: Defaults for UNIX

The UNIX-specific fields on the Operations System Specials page of the Entire Operations Defaults window 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: Existing Dynamic JCL might become invalid after changing this escape character.
Submission	Submission escape character. This escape character is prefix for symbols to be replaced at submission time. Note: Existing Dynamic JCL might become invalid after changing this escape character.

Defaults for Windows

This section describes the fields provided for Windows default settings.

Fields: Defaults for Windows

The Windows-specific fields on the Operations System Specials page of the Entire Operations Defaults window 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: Existing Dynamic JCL might become invalid after changing this escape character.
Submission	Submission escape character. This escape character is prefix for symbols to be replaced at submission time. Note: Existing Dynamic JCL might become invalid after changing this escape character.