DEFINE-ENVIRONMENT Define test environment

The DEFINE-ENVIRONMENT statement defines the test environment for simulation.

The following options can be defined for the environment:

• syntax file hierarchy (PARAMETER-FILE operand)

• procedure mode (PROC-MODE operand)

• batch or dialog mode (TASK-TYPE operand)

• behavior in the event of an error (SPINOFF operand)

• display of the standardized transfer area (DISPLAY operand)

• privileges of the task (PRIVILEGES operand).

• display of call information

DEFINE-ENVIRONMENT

PARAMETER-FILE = *STD (...) / *NO(...) / <filename 1..54 without-gen-vers>(...)

*STD(...)

USER = *STD / *NO / <filename 1..54>

*NO(...)

SYSTEM = *STD / *NO / *CURRENT / <filename 1..54>   
,GROUP = *STD / *NO / <filename 1..54>   
,USER = *STD / *NO / <filename 1..54>

<filename 1..54 without-gen-vers>(...)

USER = *STD / *NO / <filename 1..54>

,PROC-MODE = *NO / *YES

,TASK-TYPE = *DIALOG / *BATCH

,SPINOFF = *NO / *YES

,DISPLAY = *QUESTION / *NO / *SHORT / *LONG

,PRIVILEGES = *ALL / list-poss(2000): *TSOS / *SECURITY-ADMINISTRATION /

*USER-ADMINISTRATION / *HSMS-ADMINISTRATION / *SECURE-OLTP /

*TAPE-ADMINISTRATION / *SAT-FILE-MANAGEMENT / *NET-ADMINISTRATION /

*FT-ADMINISTRATION / *FTAC-ADMINISTRATION / *HARDWARE-MAINTENANCE /

*SAT-FILE-EVALUATION / *SUBSYSTEM-MANAGEMENT /

*SW-MONITOR-ADMINISTRATION / *ACS-ADMINISTRATION /

*VM2000-ADMINISTRATION / *VIRTUAL-MACHINE-ADMINISTRATION /

*SECURE-UTM / *PROP-ADMINISTRATION / *OPERATING / *STD-PROCESSING /

*POSIX-ADMINISTRATION / *PRINT-SERVICE-ADMINISTRATION

,CALL-INFORMATION = *YES / *NO

PARAMETER-FILE =
Determines the syntax file hierarchy in which the commands or statements are simulated.

PARAMETER-FILE = *STD(...)
The SDF standard parameter file is used.

USER =
Determines the user syntax file.

USER = *STD
The current user syntax file is used.

USER = *NO
No user syntax file is activated.

USER = <filename 1..54>
Name of the user syntax file that is to be activated.

PARAMETER-FILE = *NO
No parameter file is used. The user defines the syntax file hierarchy himself.

SYSTEM =
Determines the system syntax file.

SYSTEM = *STD
The current basic system syntax file is used.

SYSTEM = *NO
No system syntax file is used.

SYSTEM = *CURRENT
The current basic system syntax file and the current subsystem syntax file are used.

SYSTEM = <filename 1..54>
Name of the system syntax file that is to be activated.

GROUP =
Determines the group syntax file.

GROUP = *STD
The current group syntax file is used.

GROUP = *NO
No group syntax file is activated.

GROUP = <filename 1..54>
Name of the group syntax file that is to be activated.

USER =
Determines the user syntax file.

USER = *STD
The current user syntax file is used.

USER = *NO
No user syntax file is activated.

USER = <filename 1..54>
Name of the user syntax file that is to be activated.

PARAMETER-FILE = <filename 1..54 without-gen-vers>(...)
Name of the parameter file that is used.

USER =
Determines the user syntax file.

USER = *STD
The current user syntax file is used.

USER = *NO
No user syntax file is activated.

USER = <filename 1..54>

Name of the user syntax file that is to be activated.

If a parameter file is used for input (*STD or <filename>), the names of the system

syntax file and the group syntax file assigned to the profile ID of TSOS (SYS-TSOS) are read from the parameter file and activated for simulation.If the parameter file contains errors or if the syntax files are invalid, the system syntax file and the TSOS group syntax file with the standard names are used and messages CMD0685 and CMD0686 are output.

If the name of the system, group or user syntax file is entered and an error occurs while activating the syntax file, an error message is output. If the system syntax file or the group syntax file contains errors, the syntax files with the standard names areused. If the user syntax file is errored, no user syntax file is activated. At least one system or group syntax file must be activated, otherwise simulation is not possible as there is no global information available. If *STD is entered as the system syntax file, only the current basic system syntax file is activated.

PROC-MODE =
Determines whether procedure mode is to be simulated.

PROC-MODE = *NO
Procedure mode is not to be simulated in the test environment.

PROC-MODE = *YES
Procedure mode is to be simulated in the test environment.

In simulated procedure mode, commands must be entered preceded by a slash (/) and statements must be entered preceded by a double slash (//). Commands and statements can also be entered in lowercase letters.The spin-off mechanism can be activated following an error (see the SPINOFF operand, "DEFINE-ENVIRONMENT Define test environment"). The spin-off mechanism is stopped by entering the SET-JOB-STEP command or the STEP statement.Procedure parameters cannot be replaced.This environment makes it possible to test commands and statements that are only permitted in batch mode.

TASK-TYPE =
Determines the type of the task.

TASK-TYPE = *DIALOG
Dialog mode is used in the environment.

TASK-TYPE = *BATCH
Batch mode is used in the environment.

In simulated batch mode, commands must be entered preceded by a slash (/) and statements must be entered preceded by a double slash (//). Commands and statements can also be entered in lowercase letters. The spin-off mechanism can be activated following an error (see the SPINOFF operand, "DEFINE-ENVIRONMENT Define test environment"). The spin-off mechanism is stopped by entering the SET-JOB-STEP command or the STEP statement.This environment makes it possible to test commands and statements that are only permitted in batch mode.

SPINOFF =

Determines whether the spin-off mechanism is to be activated for errored commands or statements. This operand is used only if PROC-MODE=*YES or TASK-TYPE=*BATCH has been set.

SPINOFF = *NO
The spin-off mechanism is not activated in the event of an error.

SPINOFF = *YES
The spin-off mechanism is activated in the event of an error. To stop this mechanism, the SET-JOB-STEP command or the STEP statement must be processed.

DISPLAY =
Determines whether the contents of the standardized transfer area are displayed. This operand does not apply to commands defined with ADD-CMD...,IMPLEMENTOR= *TPR(...,CMD-INTERFACE=*STRING...) (see SDF-A).

DISPLAY = *QUESTION
Following the syntax analysis, the following query is issued for each command or statement:

% SDS0008 DO YOU WANT TO DISPLAY TRANSFER AREA? REPLY: NO/LONG/SHORT In procedures and batch tasks, DISPLAY=*QUESTION has the same effect as DISPLAY=*NO.

DISPLAY = *NO
The contents of the standardized transfer area are not displayed.

DISPLAY = *SHORT
The contents of the standardized transfer area are displayed in character format and in hexadecimal format with a line length of 80 characters per line.

DISPLAY = *LONG
In addition to the information output for DISPLAY=*SHORT, a structure description (STRUCTURED DESCRIPTION) is displayed. This contains the type, length and value of every operand and can be up to 15000 bytes long.
For a correct output to be received in the case of statements which use the normal format as of SDF V4.1 for the standardized transfer area, *STMT(...LAYOUT=*NEW) must be specified for DEFINE-TEST-OBJECT.

PRIVILEGES =
Determines the privileges which the task has in the test environment.

PRIVILEGES = *ALL
The task has all privileges.

PRIVILEGES = list-poss(2000): *TSOS / *SECURITY-ADMINISTRATION / *USER-ADMINISTRATION / *HSMS-ADMINISTRATION / *SECURE-OLTP / *TAPE-ADMINISTRATION / *SAT-FILE-MANAGEMENT / *NET-ADMINISTRATION / *FT-ADMINISTRATION / *FTAC-ADMINISTRATION / *HARDWARE-MAINTENANCE / *SAT-FILE-EVALUATION / *SUBSYSTEM-MANAGEMENT /
*SW-MONITOR-ADMINISTRATION / *ACS-ADMINISTRATION /
*VM2000-ADMINISTRATION / *VIRTUAL-MACHINE-ADMINISTRATION / *SECURE-UTM / *PROP-ADMINISTRATION / *OPERATING / *STD-PROCESSING*POSIX-ADMINISTRATION / *PRINT-SERVICE-ADMINISTRATION
The task has precisely those privileges included in this list.

CALL-INFORMATION = *YES / *NO
Defines whether call information is to be shown. The call information includes:

• a log of the command or statement

• the interface type of the command (ASS/ISL/SPL/PROCEDURE)

• the name of the entry point for TPR commands.