Previous Topic: Checkout (CO)Next Topic: Final Panel Processing


Panel Field Descriptions

Enter JOB statements

Required. Length: 1-72. Type: alphanumeric.

Enter up to four JOB CONTROL statements. These statements precede the JCL created by the Checkout model(s). Unless your models generate JOB statements, at least one // JOB CONTROL statement must be entered.

Number of Members per Job

Optional. Length: 1-2. Type: numeric.

If you want to limit the number of members grouped together per job, specify the value here. If left blank, the default is 25 members per job. If you experience system 322 abends (too much CPU time) when checking in multiple members, reducing this value can correct this.

Checkout From Lvl

Required. Length: 1-4. Type: alphabetic.

This field determines the origin of the requested From Member name. If the member has been checked in before on this Move Request (Project), enter the valid value level used by the member's Library Code and the development level. This field is filled in for you automatically. CA-PanAPT searches from the Development Test level up through your highest migration level looking for the member and supplies the first level that it finds for the member. If the member is not found, the level is blank, and the Checkout From Type value is ADD. If CA-PanAPT cannot search for the member because its access method does not have a browse exit defined, the highest active level defined to the Library Code is filled in. A blinking asterisk appears to the right of the level to indicate this.

Checkout From Type

Optional. Length: 1-4. Valid values: BKUP, BU, U, BKOT, BO, O, or ADD.

This field further determines the origin of the requested From Member name by allowing you to specify the levels Backup (BKUP, BU, U) or Backout (BKOT, BO, O) Libraries. If not specified, the primary library for the level is the origin of the Checkout. You can also specify a value of ADD indicating that you are adding a new member. When you specify ADD, the Checkout From Lvl field must be blank. Only specify ADD if your Checkout models support it. They must add a prototype member to the test library. The distributed PDS, CA-Panvalet, and CA-Librarian Retrieve models all support this.

From Member

Display only. Displays the name of the requested member to use for the copy utility.

From Data

Optional. Length: 1-8. Type: alphanumeric. Default: null ("").

This field is provided to pass data to the Checkout model. The value of this field is accessible through the $FROMDATA System Modeling Keyword.

To Member

Optional. Length: 1-10. Type: alphanumeric.

Determines the name of the copied member within the starting library. The name defaults to the From Member name. This member must not already exist in the starting library unless the Replace Member option is Y; otherwise, the Checkout JOB fails.

To Data

Optional. Length: 1-8. Type: alphanumeric. Default: null ("").

This field is provided to pass data to the Checkout model. The value of this field is accessible through the $TODATA System Modeling keyword. This data is intended to be associated with the To Member name.

Rep

Required. Length: 1. Valid values: Y or N. Default: N.

Enter Y to allow an existing To Member to be replaced on the starting library or enter N to prohibit a replace.

Lib Code

Display only. Displays the member's associated Library Code name.

Line Commands
S

Start. Enter S on the Command line to start Checkout model processing.Only the rows of the table marked with the S (select) action command are

processed.

A

All. Enter A on the Command line to start Checkout model processing on all rows of the table except those marked with the X (exclude) action command. All rows including those that are not marked (blank) are processed.

Action Commands
S

Select. The S action marks the row eligible for Checkout model processing when the S Line command is entered.

X

Exclude. The X action marks the row not eligible for Checkout model processing when the A Line command is entered.