In prior releases of CA‑PANAPT, it was common for models to only create control statements which were referenced by corresponding Move PROCs in the APJJ5320 job. Many models on the model exchange are set up this way. ABENDs could occur in these PROCs if they attempted to access these control statement members when they didn't exist, because there were no members to move in that move cycle for the Move PROC.
One way to prevent these ABENDs was to assure that there were always control statement members for the PROCs to access even if they were empty. This is accomplished using the APJRMDLO PARMLIB member. In this member you specify the names of APTMDLO members that are to be unconditionally created.
Two statement types can be specified in the APJRMDLO member, comments and member initialization statements. Comments are specified by placing an * in position one of the record. Member initialization statements are specified by placing the characters APTMDLO starting in position one followed by a member name starting in position 10, optionally followed by a comment in positions 18 through 80. Every member name specified in the APJRMDLO member exists in the APTMDLO data set when Move Modeling is complete, although they are empty if no models wrote anything to them. On‑Demand Modeling can also use a member initialization member or file simply by allocating ddname M5320F01 to one.
The APJRMDLO member distributed with CA‑PanAPT has sample and prototype statements for many of the models and Move Procs on the Model Exchange.
None of the models distributed with CA‑PanAPT require the use of the APJRMDLO parmlib member, so the APJJ5320 job does not use it. If you have models that need it, you must alter the APJP5320 PROC, uncommenting the M5320F01 DD statement in step APCS5320.
|
Copyright © 2004 CA.
All rights reserved.
|
|