Alternative 2: Allocation of the libraries as part of the TSO Logon Procedure

Create a new TSO logon procedure that has the SA z/OS data sets in the appropriate concatenations.

To create a TSO logon procedure, take an existing one and modify its DD statements to include the following:

//ISPPLIB    DD …
             DD DSN=ING.SINGPENU,DISP=SHR
             DD …

//ISPMLIB    DD …
             DD DSN=ING.SINGMENU,DISP=SHR
             DD …

//ISPSLIB    DD …
             DD DSN=ING.SINGSENU,DISP=SHR
             DD …
		
//ISPTLIB    DD …
             DD DSN=ING.CUSTOM.AOFTABL,DISP=SHR   1 
             DD DSN=ING.SINGTENU,DISP=SHR
             DD …

//ISPLLIB    DD …
             DD DSN=ING.SINGLOAD,DISP=SHR
             DD …

//SYSPROC    DD …
             DD DSN=ING.SINGTREX,DISP=SHR
             DD …

//AOFTABL    DD DSN=ING.CUSTOM.AOFTABL,DISP=SHR   1 

//AOFPRINT   DD SYSOUT=…   2 

//AOFIPDB    DD DSN=ING.SINGPDB,DISP=SHR   3

Notes:

Ensure that your ISPF temporary data sets have been allocated with enough space.
- When a build of the automation control file is performed, each file is written to the temporary data sets before it is copied into the target data set. This can lead to a temporary data set many thousands of lines long. For an enterprise with many applications, there may be several hundred thousand lines written to the temporary data set. These are in the ISPWRK data sets. See z/OS ISPF Planning and Customizing for more information, where it is recommended that you pre-allocate to VIO however, because it reduces overhead and eliminates potential problems from insufficient space.
- The ISPCTL1 temporary data set is used by SA z/OS to temporarily hold file tailoring output and to hold the JCL for batch jobs. See z/OS ISPF Planning and Customizing for more information on the ISPCTL1 data set.
The ellipses (…) in the DD statements indicate the presence of more information in the JCL: for example, other data sets in a concatenation.
User-specific data sets should be placed before the SA z/OS data sets. Generally speaking you need to take care that the concatenation of the SA z/OS data sets does not interfere with the concatenation with data sets from other products.
The AOFTABL DD statement ( 1 ) is required to store ISPF tables created when you use the customization dialog. Such tables are used, for example, during pdb import or when the administrator modifies the SA z/OS policy definitions from the SA z/OS customization dialog. This data set is also used to hold the data set definitions for batch processing. This data set was allocated by you in the sample INGEDLGA (see Step 3: Allocate Data Sets for the ISPF Dialog).
The AOFPRINT DD statement ( 2 ) is used in place of SYSPRINT for IEBUPDTE, which is invoked when a user of the customization dialog creates a policy database using an SA z/OS-supplied sample as a model. If this DD statement is not allocated, SA z/OS allocates the DD as SYSOUT=H.
If the IEBUPDTE invocation is successful and SA z/OS dynamically allocated the AOFPRINT file as SYSOUT=H, the output is purged. If the invocation fails, the output is saved for use in diagnosis of the problem.

When specifying AOFPRINT(SYSOUT(Cls)), the output of the dynamically called IEBUPDATE utility is placed in the JES output class Cls. This output is not purged.
The AOFIPDB DD statement ( 3 ) points to the SA z/OS sample library.
The AOFIPDB DD statement is required for using best practice policies and for building system operations configuration files.
You should not use any DD names starting with AOF in your logon procedure except those specified in the example above. This is because the SA z/OS customization dialog may dynamically generate AOFxxxxx DD names. Specifically, SA z/OS generates AOFIN and AOFUT2 DD names.

If you already use a CLIST to allocate your data sets for ISPF, modify it to include the SA z/OS data sets in the appropriate concatenations for users of the customization dialog. If you want to create a CLIST to allocate your data sets you should find out your current allocations for the DD names that need SA z/OS data sets allocated to them. This can be done with the LISTALC STATUS command.