Modeling Facility › Modeling and the Parts of CA-PanAPT › Models and Model Statements

Models and Model Statements

Models are stored as members of a PDS. CA‑PanAPT models consist of source statements that direct CA‑PanAPT to write 80-character images to one or more outputs. These outputs can be sequential files or members of the CA‑PanAPT APTMDLO PDS. Outputs can be written for any of the following reasons:

• To supply information for posting Move Request status.
• To create JCL and control statements to move or back out members.

  Typically, the model creates one set of members per grouping. One of these members contains JCL. Other members contain control statements. The JCL generated has DD statements referencing the control statement members.

  The Model facility provides a unique prefix per grouping that can be used to prevent different groupings from accidentally using the same members.

• To create JCL for external processing, such as compiles and link edits. The sample model provided for compiles creates one member with a single job. Each member to be compiled has its own steps in this job.

  You can use a different setup if you like, creating separate jobs for each compile, one submitting the next when it finishes.

• To create JCL for submission to the operating system as part of Retrieve processing. CA‑PanAPT creates separate jobs for each Retrieve request so that they can be handled as they occur, rather than waiting for a scheduled batch job. One job is created that includes all members requested at the same time.

  CA‑PanAPT submits Retrieve JCL to the operating system. You need not take any other action to start the Retrieve process. Retrieve models supplied with CA‑PanAPT do not write to APTMDLO members or sequential files. All information required for the Retrieve is included with the JCL.

• To create JCL for submission to the operating system to perform automated verification of a Move Request.