CA JCLCheck only uses virtual storage to process and analyze job streams. The amount of virtual storage it uses depends on the size of the JCL file it is analyzing. At some installations, CA Roscoe address space is too small to allow CA JCLCheck to process large JCL files successfully under CA Roscoe. For this reason, you can establish a statement count limit for execution of CA JCLCheck under CA Roscoe.
The ROSLIMIT(nnnn) specification defines the maximum number of statements, both from the AWS and from the PROCLIBs CA JCLCheck is going to process. When CA JCLCheck reaches this limit, it generates message CAY6172S and terminates processing. The limit count can be any value from 1 to 9999.
If you have not upgraded to CA Roscoe r5.7 or higher, you can supply a ROSLIMIT option by altering the source for RSSCJCKO on OPTION. You can specify this limit by adding it to the calling parameters in the RSSCJCK0 routine. See the source for RSSCJCK0 for detailed instructions at statement numbers 481 through 485.
If you are at CA Roscoe 5.7 or higher, you can specify the ROSLIMIT option by assembling a JCLOPTS CSECT in the RSSCJCKO module. This process is described in the CA Roscoe documentation.
Note: A statement, in CA JCLCheck terms, includes all continuation statements; therefore, the actual statement count is higher than the statement count limit you specify in the ROSLIMIT parameter.
|
Copyright © 2014 CA.
All rights reserved.
|
|