Creating a startup procedure

You can specify the amount of storage through the procedure to start the VTAM® capture point application.

Procedure

Follow these steps to estimate your storage needs and then specify them in the startup procedure.

Determine the amount of below-the-line private storage needed for the NPF VTAM capture point application. Consider the following factors when estimating this storage requirement:
1. Storage for a minimum-configuration application:
  For an NPF VTAM capture point application, the simplest useful configuration would have one logical printer LU running one session with all output routed to a single destination. The amount of below-the-line storage needed for such a configuration varies from one MVS™ system to the next.
  - For preliminary planning purposes, assume 0.5 MB will be needed for this configuration.
  - Tuning note: After NPF is installed, a simple test run with this configuration will enable you to refine that estimate. The JCL output listing from that test will show the below-the-line private storage actually used on your system.
2. Storage for active print files:
  Print files being processed by the NPF VTAM capture point application are managed as temporary QSAM data sets requiring below-the-line storage.
  - Each file being received requires 16 KB.
  Specify either the MAXFLSTG or MAXOPEN JCL parameter to limit the amount of below-the-line storage used for open print data sets. With either of these parameters, if a request for a new data set would cause that limit to be violated, that request will be rejected with a sense code indicating you had insufficient resources. For example, a limit of 1000 open files could be expressed by either MAXFLSTG=16000K or MAXOPEN=1000.
3. Other minor storage requirements:
  - Each logical printer LU requires 112 bytes of below-the-line control block storage.
  - Each session requires 112 bytes of below-the-line control block storage.
Set up the JCL to run the VTAM capture point application using the estimates calculated in the previous step. Include the following parameters on the EXEC statement.
1. Identify the program to be started.
```
PGM=EZAPPAAA
```
2. Code the REGION parameter to specify the amount of below-the-line storage calculated in the previous step. The region sizedepends on the number of active sessions and the maximum number of open print files in progress at any given time. This should include your minimum configuration requirement plus the maximum storage for active print files and other minor storage requirements.
3. Code the PARM parameter with LUCLASS, and either MAXFLSTG or MAXOPEN.
```
  ,PARM=(LUCLASS=(luclass_list),
         MAXFLSTG=file_stg_limit,
         MAXOPEN=open_file_limit)
```
  Specify luclass_list as one or more LU class numbers with values from 1 to 64. Specify file_stg_limit as the maximum amount of buffer space you want to allow for open print data sets, or specify open_file_limit as the maximum number of open print data sets.
  These LU class numbers will be used as follows to select the set of logical printer names that the application represents:
  - For each VTAM-usable entry in the routing file, the MAJKEY keyword must specify a logical printer name, and the LUCLASS value must specify one or more LU class numbers with values from 1 to 64.
  - The LU class data from the JCL will be compared to the LU class data in each routing file entry. If there is a match on at least one LU class number, the application will represent the logical printer name specified by that entry.
  For example, assume that the routing file contains 4 entries as follows:
  - PRINTERA LUCLASS=(1,4)
  - PRINTERB LUCLASS=(2,3,4)
  - PRINTERC LUCLASS=(3,4)
  - PRINTERD LUCLASS=(2,4)
  Given the above routing file entries, code the JCL LUCLASS parameter as follows:
  To use all 4 printers
  
  LUCLASS=(4)
  
  To use printers B, C, and D,
  
  LUCLASS=(2,3)
  
  To use printers B and D
  
  LUCLASS=(2)
  
  To use just printer A
  
  LUCLASS=(1)
  
  See Starting the NPF VTAM capture point for the sample JCL and a further explanation of the LUCLASS, MAXOPEN, and MAXFLSTG parameters.
4. To prevent MVS from terminating the application because of its running time, code the JOB statement with TIME=1440 or TIME=NOLIMIT.