Display only. CA-PanAPT displays the action you selected.
Display only. CA-PanAPT displays the Library Code / subcode you selected for viewing or maintaining.
Required. Length: 1 ‑ 55. Type: alphanumeric.
This field must not be left blank. CA-PanAPT performs no editing on the contents of this field. The description appears on CA‑PanAPT reports.
Optional. Length: 1-8. Type: alphanumeric.
The Type field is used to indicate the type of data sets that are processed by this Library Code. The type of data sets are used by the Development Facility and are also used by the CA‑PanAPT DB2 Option.
The Development Facility uses this field to determine what data set to use for the target of a Checkout or Checkin. The development data sets can be associated with type, so that a development data set with a type matching the Library Code's type is selected as a target. To clarify this, lets look at an example. Lets say you have two work data sets that you can check out members into. One is for JCL, and the other is for program source modules. When you are checking out a JCL member, you want to ensure it does not get checked out into your source module PDS. This is accomplished by giving your JCL Library Codes and your development JCL data sets a type of JCL. Likewise, your source module Library Codes and development data sets can be given a type of SOURCE. CA‑PanAPT matches this and picks the correct development data sets for Checkout and Checkin processing.
The CA‑PanAPT DB2 Option also uses this field to identify Library Codes that handle DB2 source modules, DBRMs, packages, and plans. These types all begin with DB2. For the complete DB2 values and more information, see the CA‑PanAPT DB2 Option Reference Guide.
This area of the panel is used to specify edit criteria concerning the member names.
Required. Length: 1. Type: numeric. Valid values: 1, 2, or 3:
the members can be renamed, but renaming is not required
2 the members cannot be renamed
3 the members must be renamed
As a member moves out of its starting level test library up to the library for the next level, it might or might not be renamed. This field controls whether the user can or must enter different names for a member for the starting level and subsequent levels in a Move Request.
Required. Length: 2. Type: numeric. Minimum length: 01 through 10 with default of 01. Maximum length: 01 through 10 with default of 08.
Entries in these fields force length editing of the names of members added to Move Requests. The values typed into these fields must be greater than or equal to one, and less than or equal to ten.
The maximum length must be equal to or greater than the minimum length. If the minimum and maximum lengths are equal, all member names using this Library Code are the same length.
When entering the numbers, they must be right‑justified and zero‑filled.
When creating a Move Request, User Data fields are optional fields that can be used to retain additional information about each member. These optional fields are available for use by models. There are two User Data fields, one for the From member name and one for the To member name.
CA-PanAPT models and Member Existence exits can use this data. Specific values for models and Member Existence exits supplied with CA‑PanAPT are discussed in the "Setups for Different Types of Moves" chapter. If your site uses other exits, your CA‑PanAPT Administrator must tell you what they require.
You can indicate a minimum and a maximum length for these User Data fields in the Library Code data.
Required. Length: 2. Type: numeric. Minimum length: 00 through 08 with default of 00. Maximum length: 00 through 08 with default of 00.
The maximum length must be greater than or equal to the minimum length. If the minimum and maximum lengths are equal all user data is the same length.
A maximum length of 00 indicates that no user data can be entered.
|
Copyright © 2004 CA.
All rights reserved.
|
|