Display only. CA-PanAPT displays the action that you selected.
Display only. CA‑PanAPT displays the short name of the level being processed.
Display only. CA-PanAPT displays the Library Code / subcode that you selected for viewing or maintenance.
Required. Length: 1‑44. Type: alphanumeric.
Enter the data set names of the actual libraries. These must be standard OS data set names of the libraries to be assigned to the level. CA-PanAPT does not edit the data for syntax or to ensure that the data set names entered match the data sets entered in any JCL. It is the user's responsibility to ensure correctness.
The Backup data set names must be unique within the Library Code. They cannot match any other Target, Backup or Backout data set name within the Library Code.
The Backout data set name must not match the Target data set name for the current level or any subsequent levels. It can, however, match the Target data set name for a prior level. This way, upon completion of a Back Out, the failing members can be put directly back into your test libraries.
Required. Length: 1‑8. Type: alphanumeric. Default: see below.
Enter the ddnames that CA-PanAPT uses in the batch utility steps while moving/deleting members. These must be standard OS ddnames. CA‑PanAPT does not edit the data to ensure that the ddnames entered match the actual ddnames used in any JCL. The Models and exits used by this Library Code may or may not use the ddnames that you specify.
CA‑PanAPT generates default ddnames on the panel for each library in the level. The default ddnames generated are the 1‑ to 7-character Library Code/subcode followed by the ddname suffix defined to the level. In addition, a B or O is appended for Backup and Back Out libraries respectively. If the B or O does not fit in the 8-character field, you are prompted for a unique ddname.
For example: If you are adding the QA level to Library Code PROC, and the ddname suffix for the QA level is Q, the ddnames generated are PROCQ, PROCQB, and PROCQO for the primary, Backup, and Back Out libraries respectively.
You can type over the generated defaults if you want to change them.
Optional. Length: 1‑10. Type: alphanumeric.
Enter any required password or control field required for the libraries. CA‑PanAPT does not edit the data entered in any way.
The Security field is used by the model processing. It is model‑dependent.
Examples of entries into this Security field are a CA‑Panvalet control code or a special password.
Note: The security data is only displayed on inquiries by users authorized to view the Security fields. Authorization is controlled by the LIBCODE/SECURITY activity record.
Optional. Length: 1-2. Type: alphanumeric.
This field describes the Access Method required to process the data set. Only Access Methods defined using Control File maintenance can be specified. A list of these Access Methods can be obtained by entering the AM command and pressing ENTER. You can then select an Access Method from the list presented by the AM command, rather than typing it in. If you enter an Access Method then you can specify an equal sign (=) for the exit names on this panel to imply the Access Methods registered exit name.
Required except for starting level, in which case it is not available and displayed.
Valid values: C (Copy), M (Move), D (Delete), and I (Inactive).
This field controls how movement is to occur when moving members into this level.
Indicates that the members are copied to this level's data set. The members still reside in the previous level's data set.
Indicates the members are moved to this level's data set. The members are removed from the previous level's data set.
Indicates the members are not moved to this level, and they are deleted from the previous level's data set. Use caution with this value. This value might be used in the following scenario. You have one Library Code that moves program source code and another that moves load modules. When moving into your quality assurance level you want to recompile the source and recreate the load modules, but from that point on you just want to move the load modules. The Library Code for the source program has modeling specifications that cause the load module to be created from a compile and link at the quality assurance level. Your Library Code for the load module you use this value at the quality assurance level to clean up the test level's load library.
Indicates that this level is inactive and does not get used in any moves. It is as though it were not defined to the Library Code. This can be useful if you are planning to implement a new level on a particular date and want to be as ready as possible. I (Inactive) is used only if there are no outstanding move requests.
Required if you have a Backup DSN. Valid values: Y (Yes) or N (No).
This field indicates whether CA‑PanAPT backs up members in the target DSN before replacing them on a move.
This field might appear to be redundant, for the simple existence of a Backup DSN should indicate that backup is enabled. It is supplied for compatibility with earlier releases of CA‑PanAPT, where Models were written that place other data in the Backup or Backout DSN.
Note: This field must be a Y if Back Out is to be supported.
Required if you have a Backout DSN. Valid values: B (Backout and restore), R (Restore without backout), and P (Prohibited).
This field indicates what action takes place during a Backout.
Indicates that the current members being backed out are saved on the Backout DSN, and then the previous members on the Backup DSN are moved back to the Target DSN. This is the most frequently used option.
Indicates the previous members on the Backup DSN are moved to the Target DSN without first saving the current members on the Backout DSN. The members being backed out are not saved anywhere. Use this option with caution. Make sure there is a copy of the members being backed out somewhere else.
Indicates that Backout is prohibited. The Backout DSN field is not used by CA‑PanAPT if you specify this option, but is still available to Models. Many Models have been written under earlier releases of PanAPT that place other data in the Backout DSN field; this option allows that data to be placed there.
Note: If you do not specify a Backout DSN and leave this field blank, it is treated as P (Prohibited).
Required. Length: 20. Valid values: Y (Yes) or . (period) in each position:
In the column of the associated verification category indicates the verification category is required for this level. For the starting level, Verification Requirements must be satisfied before the Move Request can be closed. For all other levels, the Verification Requirements must be satisfied before the move to that level can take place.
For example, if the Quality Assurance level requires Verification Category 4 before a move can take place, enter a Y in the fourth column for the Quality Assurance level. After the Move Request has been closed and has been moved to the level prior to Quality assurance, the Quality Assurance Move waits for this Verification Requirement to be satisfied.
If your Quality Assurance level is the first level after your starting test level, you can, as an alternative, enter a Y in the fourth column for the starting test level. In this case, the Move Request cannot be closed until this Verification Requirement has been satisfied.
In the column indicates the verification category is not required.
The panel initially displays with a . in each verification column. Only Verification Categories which are defined in the Control File System Information can be specified as Y. See the "Control File" chapter for more information.
Note: You can display descriptions of the Verification Procedure categories by entering VC on the Command line.
Required. Length: 20. Valid values: Y (Yes) or . (period) in each column:
In the column of the associated approval category indicates the approval category is required for this level's moves. For example, if a Library Code requires Approval Category 4 before a move to Quality Assurance can take place, enter a Y in the fourth column for the Quality Assurance level.
In the column indicates the approval category is not required. The panel initially displays with a . in each approval column.
Note: You can display descriptions of the Approval Categories by entering the AC command on the Command line.
Required. Length: 20. Valid values: Y (Yes) or . (period) in each column:
In the column of the associated approval category indicates the approval category is required for this level's Back Outs. For example, if a Library Code requires Approval Category 4 before a Back Out at the Quality Assurance level can take place, enter a Y in the fourth column for the Quality Assurance level.
In the column indicates the approval category is not required. The panel initially displays with a . in each approval column.
Note: You can display descriptions of the Approval Categories by entering the AC command on the Command line.
Optional. Length: 1-8. Type: alphanumeric.
The program entered in this field is called when a Member Selection List (MSL) is requested from a Move Request member add, and it is used to read the directory of the level's primary library and build the MSL. You can enter an equal sign (=) to indicate the MSL exit program defined to the Access Method is to be used. If this field is blank, you cannot request a MSL for this Library Code at this level.
Note: You must specify this exit, the Exist exit, and the Browse exit if you are using the Development Facility with this library code.
The following shows the sample MSL exit programs distributed with CA‑PanAPT.
|
Exit Name |
Library Type |
|---|---|
|
APAS0600 |
CA‑Panvalet |
|
APAS0610 |
PDS |
|
APAS0620 |
CA‑Librarian |
Optional. Length: 1-50. Type: alphanumeric.
Enter the parameter to be passed to the MSL exit. None of the sample exits require user parameters.
CA-PanAPT provides several sample exit programs that can be used by the online system to validate that members do exist in the sending libraries. This prevents specification of non‑existent member names in a Move Request.
Note: You must specify this exit, the MSL exit, and the Browse exit if you are using the Development Facility with this library code.
Each of these sample programs validates a member by determining if it exists in the library from which it is moved. For a move from the Test to QA level, the exit specified at the Test level verifies that the member is in the Test library. On a Back Out at the QA level, the exit specified at the QA level verifies that the member is in the QA Backup library. The following shows a sample of exit programs and the associated library type.
|
Exit Name |
Library Type |
|---|---|
|
APAS0200 |
PDS |
|
APCS0221 |
CA‑Librarian |
|
APAS0222 |
CA-Panvalet |
|
APAS0223 |
CA-Panexec |
|
APAS0226 |
CA-Telon |
Your site might have developed other Member Existence exits. Your CA‑PanAPT Administrator can provide you with their names and information about their functions.
Optional. Length: 8. Type: alphanumeric.
Enter the name of an exit to verify existence of members. You can enter an equal sign (=) to indicate the existence exit program defined to the Access Method is to be used.
Member existence is checked in the daily move job (APJJ5310). If any members fail the existence check for a Move, the move is not allowed to proceed. If any members fail the existence check for a Back Out, the Back Out proceeds without backing out those members.
In addition, if an existence exit is specified for the starting test level, member existence is also checked online. Move Requests cannot be closed if any members fail the existence check at the starting level.
Optional. Length: 50. Type: alphanumeric.
This field is used to pass a user parameter to the member existence exit program.
Except for APAS0223, the exit for CA‑Panexec libraries, none of the sample exits require user parameters. See CA‑Panexec Moves in the "Setups for Different Types of Moves" chapter. If your site has developed its own exits, your CA‑PanAPT Administrator can tell you about the parameters they require.
CA‑PanAPT provides several exit programs that can be used to view or browse members. Members can be browsed from the Development Facility and while adding members to Move Requests from a library MSL.
Note: You must specify this exit, the MSL exit, and the Exist exit if you are using the Development Facility with this library code.
Optional. Length: 1‑8. Type: alphanumeric.
Enter the name of a browse exit program to view members. You can enter an equal sign (=) to indicate the browse exit program defined to the Access Method is to be used.
The following table shows the browse exit programs provided with CA‑PanAPT:
|
Exit Name |
Library Type |
Source Provided |
|---|---|---|
|
APCS1410 |
PDS |
Yes |
|
APCS1411 |
CA‑Panvalet |
No |
|
APCS1412 |
CA‑Librarian |
No |
Optional. Length: 1‑50. Type: alphanumeric.
Enter the parameter to be passed to the Browse exit. None of the Browse exits provided with CA‑PanAPT require a parameter.
|
Copyright © 2004 CA.
All rights reserved.
|
|