The CA‑PanAPT Modeling Facility lets you create customized JCL and utility control statements for each type of batch move that needs to be done. The actual model might contain CA‑PanAPT commands, operating system JCL, and utility control statements. The CA‑PanAPT model file is a standard PDS.
The Modeling Facility uses CA‑PanAPT models to generate the JCL and/or control statements that are used to move members from one library to another.
A model is a series of 80‑character statements. The statements are either CA‑PanAPT Control Statements or Data Statements. CA‑PanAPT Control Statements use simple logic and keywords to control the generation of the output statements. The Data Statements are either the exact output lines to be generated or a skeleton that is filled in by CA‑PanAPT and then generated as output.
CA‑PanAPT Model Control statements generate output statements. As part of the batch processing of Move Requests, CA‑PanAPT reads a model, accesses fields from CA‑PanAPT files, and substitutes values from these fields and other user‑defined variable values into the model.
The base CA‑PanAPT product provides sample models for moving CA‑Librarian, CA‑Panvalet, CA‑Panexec, or PDS members. If you need a customized model, you can either copy one of the provided samples and make the necessary changes, or write your own model. Models are stored on the PDS APTMODEL. They can be set up, copied, and modified by any editor that can edit standard PDS members. The CA‑PanAPT Model Exchange file contains a wide variety of special-purpose models.
Specific requirements for move models supplied with CA‑PanAPT are discussed in the "Setups for Different Types of Moves" chapter in the CA‑PanAPT Reference Guide. Retrieve models supplied with CA‑PanAPT are described in the "Retrieve Processing" chapter of the CA‑PanAPT Reference Guide.
Models can be shared between Library Codes that use the same type of library. A Library Code can invoke several models.
|
Copyright © 2004 CA.
All rights reserved.
|
|