Starting colony address spaces outside of JES

If you do not want colony address spaces to be started under JES (which is the default), you can change this by including the SUB=MSTR parameter with the ASNAME keyword. The ASNAME keyword is specified as:

ASNAME(procname,'start_parms')

where:

The first value is required and is a 1-to-8-character name in SYS1.PROCLIB.
The second value is optional and is a quoted string that is appended to the procname when the address space is started. The string can be up to 100 characters long.

The start_parms are not validated; they are just passed to the system when the address space is started with an internal start command as in procname,start_parms. For example:

ASNAME (NFSCLNT,'SUB=MSTR')

The colony address space runs outside of JES control and does not have to be stopped if JES has to be stopped, which facilitates planned shutdowns of individual systems in a sysplex that has shared file systems. The NFS Client, TFS, and zFS physical file systems support running outside of JES and the following information might help you to decide whether to move these z/OS UNIX colonies outside of JES. The DFS Client PFS does not support being started outside of JES.

z/OS UNIX colony address spaces are started procedures. If you do not want to run them under JES, you will need to change any DD SYSOUT= data sets that are specified in these procedures. These must be changed because SYSOUT data sets are only supported under JES. There are three ways you can change these data sets:

Direct the output to a named data set by changing to DD DSN=.
Direct the output to a named file by changing to DD PATH=.
Throw the output away by changing to DD DUMMY.

Restriction: If the NFS or zFS colony address space is started at IPL time, then PATH= cannot be used because the MOUNT statements have not been processed yet.

Additionally, there are some DD names that Language Environment® will open under certain conditions. If these data sets have not been allocated in the procedure, Language Environment dynamically allocates them with SYSOUT=. The DD names are:

SYSIN: For standard input.
SYSPRINT: For standard output. If SYSPRINT does not exist, Language Environment looks for SYSTERM or SYSERR. If one of those exists, it will be used. But Language Environment does not dynamically allocate either SYSTERM or SYSERR.
SYSOUT: For standard error. It is also the default message file DD.
CEEDUMP: For capturing dumps formatted by Language Environment

If any of these names are not currently used in the colony procedure, you must add them with DD DUMMY.

If any of the existing DD SYSOUT= statements are not changed, or any of those dynamically allocated by Language Environment are not added, and an attempt is made to open that DD name, the result will be an ABENDS013. Exactly which DD names are opened and when varies by name and product and the situation.

There are also other consequences of running outside of JES that you might need to consider:

SDSF displays will not list the colony address space.
There will be no JOBLOG or system messages data set.
System messages will go to SYSLOG.
SMF recording is different between JES and the master subsystem.

For information about setting up security for the colony address space, see Step 6.