Library Conversion Utilities for CA Panvalet or CA Librarian

2
ce18
2
Library Management Conversion Process
The library management conversion process encompasses a combination of
CA Endevor
utilities and programs that allow you to load CA Panvalet or CA Librarian files into
CA Endevor
. The loaded elements adopt the language attribute and comment or description associated with the source entity as the
CA Endevor
type and comment.
There are three phases to the library management conversion process:
  • Analyze (
    CA Endevor
    Inventory Analyzer)
    Analyzes the members in your CA Panvalet or CA Librarian files, creating load SCL for input into
    CA Endevor
    . It is assumed that you have already run the
    CA Endevor
    Inventory Analyzer against your inventory, and that you have identified the
    CA Endevor
    inventory structure--that is, environments, systems, subsystems, and, optionally, processor groups--that will be assigned to each element.
  • Load (
    CA Endevor
    Load utility)
    Loads appropriate members into
    CA Endevor
    .
  • Validate (Member Validation Program)
    Validates that all members in a single data set exist in a specified
    CA Endevor
    environment.
CA Panvalet Libraries
The maximum number of CA Panvalet libraries that
CA Endevor
can open at one time is 16. Therefore, the number of open data sets in one ANALYZE statement is restricted to 16. There is no limit to the number of ANALYZE statements you can use, however. If you have more than 16 CA Panvalet libraries, use a second ANALYZE statement to scan the additional libraries.
Supersets (Panvalet Only)
Supersets apply to CA Panvalet only.
The analysis phase of the conversion process produces a reference data set that contains a list of members. These members have been analyzed for specific information; analysis is done alphabetically. During this phase, the conversion process identifies members that are supersets as well as members that reference supersets. Appropriate messages are returned when the list is generated, as shown in the following table:
Member
Message
Is a superset
CAE$0003 MEMBER member name IS A SUPERSET
Is not a superset
No message
References a member that has already been analyzed and is a superset
CAE$0004 MEMBER member name REFERENCES
SUPERSET superset name
References a member that is a superset but has not yet been analyzed
No message
Example: Handling Supersets
To illustrate how the conversion process handles supersets, assume you have a file with 26 members, A-Z. The members are analyzed and messages are issued as follows (see the previous table to match the message with the message number):
Member
Is a superset?
References a superset?
Issues this message
A
Yes
No
CAE$0003
B
No
No
No message
C
No
Yes (Member A)
CAE$0004
D
No
Yes (Member Z)
No message
E
No
No
No message
.
.
.
.
.
.
.
.
.
.
.
.
Z
Yes
No
CAE$0003
When Member Z is analyzed, the only message issued indicates that the member is a superset. No message is issued indicating that Member D references Member Z.
CA Endevor
does not “backtrack” to issue a message when a previously referenced superset is analyzed.
Analyze Phase
This section describes the first phase of the conversion process that analyzes the members in your inventory to identify the following:
  • INCLUDE members
  • COPY members
  • Members that are supersets
  • Members that reference supersets
This analysis is performed by the
CA Endevor
Inventory Analyzer, which is invoked by the conversion job stream. The conversion job stream consists of four steps, briefly described as follows:
  1. Delete SCL output data sets. In this step, existing output data sets are deleted so new ones can be created.
  2. Build reference data set. In this step, a list of analyzed members is created that will be used as input in the next step.
  3. Identify INCLUDE and COPY members, and build SCL. In this step, INCLUDE and COPY members are identified using the information generated in the previous step. Load SCL is created for input into
    CA Endevor
    .
  4. Identify superset members. In this step, superset member and unresolved members (members referenced but not found) are identified.
Submit the job stream for execution when all information has been entered for all four steps.
Conversion Job Stream
The conversion job stream is provided with your installation materials. Execution of the job stream does not change any information or processes. Because the job stream only creates input for the Load utility, you can rerun it as often as necessary should you encounter any problems.
The conversion job stream is contained in member ENJSUCNV in the JCLLIB provided on the installation tape.
Throughout the conversion job stream, there are several statements that begin with the words ESTABLISH TYPE. These statements are the rules used by the
CA Endevor
Inventory Analyzer to identify members that contain INCLUDE or COPY statements and to classify the members with a
CA Endevor
type. These rules are the only rules needed for the conversion process. Do not change these rules.
Element Classification
In Step 3 of the conversion job stream,
CA Endevor
location and inventory information is designated for the members in the reference data set.
  • You identify the
    CA Endevor
    environment, system, subsystem, and, optionally, processor group to be assigned to each member. The inventory locations must be defined to
    CA Endevor
    . You must know how you will classify the members before you begin the conversion process.
    If CCIDs are required, you must also specify a CCID to be associated with the element.
  • The element name is the same as the library member name.
  • CA Endevor
    elements require a type. The conversion job stream identifies the element type to be assigned to the member.
    The job stream takes the language attribute associated with the CA Panvalet or CA Librarian member. That attribute is prefixed with I, if it is an INCLUDE statement or C, if it is a COPY statement. The entire value becomes the
    CA Endevor
    element type.
    For example, if the CA Panvalet language is COBOL and the member is an INCLUDE, the type assigned is ICOBOL.
    If you are a CA Librarian user, there may be members in your library that do not have a language associated with them. Check the SCL that is generated by the conversion job stream. If no language is assigned, one of two TYPE values appears:
PROC Definition
This section describes the PROC definition portion of conversion job stream and the variables for which you need to provide values before submitting the job.
The following JCL shows the PROC definition portion of the conversion job stream:
// (JOBCARD) //* //********************************************************************* //*  THIS JCL MUST BE TAILORED PRIOR TO SUBMITTING THIS JOB     * //*                                  * //*   1. CHANGE TDISK TO A UNIT NAME FOR WORK DASD ??       * //*     FOR BEST PERFORMANCE, SPECIFY A VIO DEVICE        * //*                                  * //*     CHANGE iprfx.iqual TO YOUR 
CA Endevor
 INSTALL PREFIX   * //*                                  * //*                                  * //*   2. CHANGE PDISK TO A UNIT NAME FOR DATA SETS WHICH     * //*     WILL CONTAIN 
CA Endevor
 LOAD SCL STATEMENTS USED FOR   * //*     INPUT INTO THE 
CA Endevor
 LOAD UTILITY JOB        * //*                                  * //*     CHANGE PVOLSER (OR REMOVE VOL=SER=PVOLSER) TO A VALID  * //*     VOLUME SERIAL NUMBER                   * //*                                  * //*     CHANGE UPRFX.UQUAL TO THE APPROPRIATE INDEX LEVELS    * //*     AT YOUR SITE                       * //*                                  * //*   3. TAILOR THE THREE LINES THAT CONTAIN THE TEXT       * //*     'DSN1' 'DSN2' 'DSN3' TO REFLECT THE ACTUAL LIBRARY    * //*      NAMES FROM WHICH YOU ARE CONVERTING.          * //*                                  * //*                                  * //*   4. ON THE ASSIGN STATEMENT USED IN STEP TWO, SPECIFY    * //*     THE ACTUAL ENVIRONMENT, SYSTEM, SUBSYSTEM, STAGE ID   * //*     AND CCID VALUES THAT ARE TO BE USED TO CONSTRUCT THE   * //*     LOAD UTILITY SCL.                    * //*                                  * //********************************************************************* //ANALYZE PROC //* //C1BM7000 EXEC PGM=NDVRC1,PARM=C1BM7000 //     DYNAMNBR=1500,REGION=4096K //* //CONLIB  DD DSN=iprfx.iqual.CSIQLOAD,DISP=SHR //* //C1TPDD01 DD UNIT=tdisk,SPACE=(CYL,3), //      DCB=(RECFM=VB,LRECL=260,BLKSIZE=6160) //C1TPDD02 DD UNIT=tdisk,SPACE=(CYL,5), //      DCB=(RECFM=VB,LRECL=260,BLKSIZE=6160) //C1TPLSIN DD UNIT=tdisk,SPACE=(CYL,3), //      DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160) //C1TPLSOU DD UNIT=tdisk
,
SPACE=(CYL,5) //C1PLMSGS DD SYSOUT=* //********************************************************************* //* OUTPUT DATA SETS                         * //********************************************************************* //C1MSGS1 DD SYSOUT=* //C1SUMARY DD SYSOUT=* //C1PRINT DD SYSOUT=*,DCB=(RECFM=FBA,LRECL=121,BLKSIZE=6171) //SYSABEND DD SYSOUT=* //SYSOUT  DD SYSOUT=* //BSTERR  DD SYSOUT=* //     PEND
Tailor this JCL by providing values for all occurrences of the following variables:
  • iprfx
    Highest-level qualifier used to assign data set names for installation files at your site.
  • iqual
    Second-level qualifier used to assign data set names for installation files at your site.
  • tdisk
    Unit name for temporary disk data sets.
How to Delete Output Data Sets
This section describes Step 1 of the conversion job stream that deletes the existing output data sets.
The following JCL shows Step 1 of the conversion job stream:
//STEP1  EXEC PGM=IDCAMS //********************************************************************* //* DELETE SCL OUTPUT DATA SETS                   * //********************************************************************* //SYSPRINT DD SYSOUT=* //SYSIN  DD *  DELETE uprfx.uqual.INCL.SCLSTMTS  DELETE uprfx.uqual.NONINCL.SCLSTMTS  SET MAXCC = 0
The Load SCL created in Step 3 of the conversion job stream is written to one of the following data sets:
uprfx.uqual.INCL.SCLSTMTS uprfx.uqual.NONINCL.SCLSTMTS
Each time you run this job stream, new data sets are created. Step 1 deletes the existing data sets so the new data sets can be created without a problem.
Tailor the JCL by providing values for the following variables:
  • uprfx
    Highest-level qualifier used to assign data set names for
    CA Endevor
    user files at your site.
  • uqual
    Second-level qualifier used to assign data set names for
    CA Endevor
    user files at your site.
How to Build Reference Data Set
This section describes Step 2 of the conversion job stream that creates a reference data set by analyzing members in specified data sets.
The following JCL shows Step 2 of the conversion job stream:
//STEP2  EXEC ANALYZE //********************************************************************* //* BUILD REFERENCE DATASET                                           * //********************************************************************* //BSTPUNCH DD DSN=&&BSTPUNCH.,DISP=(NEW,PASS,DELETE), //      UNIT=tdisk,SPACE=(TRK,(20,10),RLSE), //      DCB=(RECFM=FB,LRECL=200,BLKSIZE=22000) //BSTIPT01 DD *  ANALYZE MEMBER *    
FROM DSNAME 'DSN1' 'DSN2' 'DSN3'
 . //BSTRULES DD * ESTABLISH TYPE INCLUDE GROUP INCLUDE WHEN  LIB = INCLUDE OR PAN = INCLUDE. ESTABLISH TYPE INCLUDE GROUP COPY WHEN  LIB = COPY. ESTABLISH TYPE REMAINDR GROUP THATSALL WHEN  PAN = '' AND LIB = ''. DEFINE PAN INCLUDE WHEN  '&C1FDSN$IO'. = 'PAN' AND  SOURCE TEXT CONTAINS  '++INCLUDE' IN COLUMN 8 INVOKE EXIT=C1BM7CAE  . DEFINE LIB INCLUDE WHEN  '&C1FDSN$IO'. = 'LIB' AND  SOURCE TEXT CONTAINS  '-INC' IN COLUMN 1 INVOKE EXIT=C1BM7CAE  . DEFINE LIB COPY WHEN  '&C1FDSN$IO'. = 'LIB' AND  '&C1FDSN$LANG'. = 'CBL' AND  SOURCE TEXT CONTAINS  ' COPY ' IN COLUMNS 7 THROUGH 68      INVOKE EXIT=C1BM7CAE WITHOUT      '*' IN COLUMN 7 LINE CURRENT  . //* //*
Step 2 creates a list of members that have been analyzed to determine whether they are INCLUDE members, COPY members, supersets, or members that reference supersets. You indicate the names of the data sets to be analyzed.
If more than one FROM data set is specified and if the same member exists in more than one data set, the program takes the first occurrence of the member. The analyzed members are listed alphabetically, as detail records in a reference data set. The reference data set is used as input for the next step in the conversion process.
Tailor the JCL by providing values for the following variables:
  • tdisk
    Unit name for temporary disk data sets.
  • DSN1, DSN: hp1.2,...DSNn
    The name(s) of the data sets you want scanned. You can code up to 16 names per ANALYZE statement.
Two types of records are created in this step: a header record and detail records. The header record assigns symbolic names to the data in the detail records. Each detail record contains the information listed as follows, in the order shown, for each unique occurrence of the member:
  • Member name
  • Library data set name
  • Yes and no (Y/N) indicators for the following:
    • Was the member selected for processing?
    • Was the member referenced by another member?
    • Was the member referenced as an INCLUDE statement?
    • Was the member referenced as a COPY statement?
    • Is the member a superset?
    • Does the member reference a known superset?
  • Language
  • Comment
Example: A Typical Record in the Reference Data Set
The following example illustrates a typical record in the reference data set:
Typical Record in the Reference Data Set
Typical Record in the Reference Data Set
How to Build Load SCL
This section describes Step 3 of the conversion job stream that creates the Load SCL.
The following JCL shows Step 3 of the conversion job stream:
//STEP3  EXEC ANALYZE //********************************************************************* //* IDENTIFY INCLUDE AND COPY MEMBERS, BUILD LOAD SCL                 * //********************************************************************* //BSTPUNCH DD DSN=&&BSTPUNCH.,DISP=(OLD,PASS) //INCLMBRS DD DSN=uprfx.uqual.INCL.SCLSTMTS,DISP=(,CATLG), //      UNIT=pdisk,vol=ser=pvolser,SPACE=(TRK,(3,2),RLSE), //      DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PS) //PGMMBRS DD DSN=uprfx.uqual.NONINCL.SCLSTMTS,DISP=(,CATLG), //      UNIT=pdisk,vol=ser=pvolser,SPACE=(TRK,(3,2),RLSE), //      DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PS) //BSTIPT01 DD * *  
SET ASSIGN
  ENV = 'ENVNAME'   SYS = 'SYSNAME'   SBS = 'SBSNAME'   CCID = 'CCID' . *  SET REFERENCE DDNAME BSTPUNCH. *  ANALYZE MEMBER *    FROM DSNAME 'DSN1' 'DSN2' 'DSN3'  . * //BSTRULES DD * DEFINE INCLUDE SUPERSET WHEN  '&CAESUPER'. EQ 'Y'  . ESTABLISH TYPE COPY GROUP NOPROC WHEN  '&CAECOPY'. = 'Y' AND INCLUDE NOT = SUPERSET  . ESTABLISH TYPE INCLUDE GROUP NOPROC WHEN  '&CAEINC'. = 'Y' AND INCLUDE NOT = SUPERSET  . //BSTMODEL DD * %DDNAME=INCLMBRS,COND=SUCCESS  LOAD MEMBER &C1MEMBER   FROM DSNAME '&C1FDSN'.   TO ENVIRONMENT &ENV.     SYSTEM    &SYS.     SUBSYSTEM  &SBS.     TYPE     &C1ELTYPE(1.,1)&CAELANG(1.,7)   OPTIONS CCID '&CCID'.     COMMENT '&CAEDESC'.  . %DDNAME=PGMMBRS,COND=FAILURE  LOAD MEMBER &C1MEMBER   FROM DSNAME '&C1FDSN'.   TO ENVIRONMENT &ENV.     SYSTEM    &SYS.     SUBSYSTEM  &SBS.     TYPE     &CAELANG(1.,8)   OPTIONS CCID '&CCID'.     COMMENT '&CAEDESC'.
Step 3 identifies the INCLUDE members and COPY members within the data sets indicated. This step also assigns
CA Endevor
location and inventory information to the members and creates the SCL used to load members into
CA Endevor
.
Each SCL statement is written to one of two data sets, depending on whether the member is an INCLUDE or COPY member or neither:
  • If the member is an INCLUDE or COPY member, it is written to the data set uprfx.uqual.INCL.SCLSTMTS.
  • If the member is not an INCLUDE or COPY member, it is written to the data set uprfx.uqual.NONINCL.SCLSTMTS.
Tailor the JCL by providing values for the following variables:
  • uprfx
    Highest-level qualifier used to assign data set names for
    CA Endevor
    user file at your site.
  • uqual
    Second-level qualifier used to assign data set names for
    CA Endevor
    user files at your site.
  • pdisk
    Unit name for permanent disk data sets. These data sets will contain
    CA Endevor
    Load SCL statements.
  • pvolser
    Volume serial number of the disk. Either enter a valid volume serial number or delete the parameter VOL=SER=PVOLSER.
  • ENVNAME
    Environment name.
  • SYSNAME
    System name.
  • SBSNAME
    Subsystem name.
  • CCID
    CCID to be associated with the element.
  • DSN1, DSN2,...DSN
    n
    The name(s) of the data sets you want scanned. Use the same data set names you coded in Step 2.
    You
    must
    enter the data set names in the same sequence as they were entered in Step 2.
CA Endevor
creates SCL for the
CA Endevor
Load utility. The SCL is formatted according to one of the two output model definitions that are included in this step of the conversion job stream. An output model definition is simply a template that defines the format of the load commands.
The first output model definition is used for members that are INCLUDE or COPY members. The second output model definition is used for members that are not INCLUDE or COPY members.
Load Syntax Variables
The output model definitions appear after the line //BSTMODEL DD *. Note the values that begin with an ampersand (&) information are provided for these values as follows:
  • &C1MEMBER (Member name)
    Reference data set
  • &C1FDSN (FROM data set name)
    Reference data set
  • &ENV (Environment name)
    SET ASSIGN parameter
  • &SYS (System name)
    SET ASSIGN parameter
  • &SBS (Subsystem name)
    SET ASSIGN parameter
  • &C1ELTYPE (1,1) INCLUDE (I) or COPY (c)
    Reference data set.
  • &CAELANG (1,7)-
    CA Endevor
    type
    CA Panvalet or CA Librarian language directory
  • &CCID (CCID associated with the member)
    SET ASSIGN parameter
  • &CAEDESC (Comment associated with the member)
    CA Panvalet comment or CA Librarian description
  • &CAELANG (1,8)-
    CA Endevor
    type
    Reference data set (if not an INCLUDE or COPY member)
How to Identify Superset Members
This section describes Step 4 of the conversion job stream that identifies the superset members.
The following JCL shows Step 4 of the conversion job stream:
//STEP4  EXEC ANALYZE //********************************************************************* //* IDENTIFY SUPERSET MEMBERS                    * //********************************************************************* //BSTIPT01 DD *  SET REFERENCE DDNAME BSTPUNCH.  ANALYZE MEMBER *    
FROM DSNAME 'DSN1' 'DSN2' 'DSN3'
 . //BSTRULES DD * ESTABLISH TYPE SUPERSET GROUP NOPROC WHEN  '&CAESUPER'. EQ 'Y'  . //BSTMODEL DD * %DDNAME=SUPERSET,COND=SUCCESS  MEMBER &C1MEMBER IN DATASET '&C1FDSN'. IS A SUPERSET MEMBER. %DDNAME=NOTSUPER,COND=FAILURE  MEMBER &C1MEMBER IN DATASET '&C1FDSN'. IS NOT A SUPERSET MEMBER. //BSTPUNCH DD DSN=&&BSTPUNCH.,DISP=(OLD,DELETE) //SUPERSET DD SYSOUT=*,DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PS) //NOTSUPER DD SYSOUT=*,DCB=(RECFM=FB,LRECL=80,BLKSIZE=6160,DSORG=PS)
Step 4 identifies those members that are supersets and any members that are unresolved. A member is considered unresolved when it has been referenced as part of an INCLUDE statement but cannot be found.
For this step, you need only code the data set names you used in Step 2 and Step 3. You
must
enter the data set names in the same sequence as entered in the previous steps.
For unresolved members,
CA Endevor
writes messages to the Execution Log, identifying the member by member name.
For superset identification,
CA Endevor
writes messages to one of two DDnames, depending upon whether a member is a superset.
  • If the member is a superset, the following message is written to DDname SUPERSET:
    MEMBER
    member-name
    IN DATASET
    dataset-name
    IS A SUPERSET MEMBER.
  • If the member is not a superset, the following message is written to DDname NOTSUPER:
    MEMBER
    member-name
    IN DATASET
    dataset-name
    IS NOT A SUPERSET MEMBER.
Load Phase
The second phase of the conversion process loads the members classified in the first phase into
CA Endevor
.
The first phase of the conversion process classified members according to whether the member was an INCLUDE or COPY statement and created Load SCL. The Load SCL was then written to one of two data sets, depending on whether the members were INCLUDE or COPY members, or neither. The next step in the conversion process is to load these members directly into
CA Endevor
, which is done using the
CA Endevor
Load utility.
Load Utility
The
CA Endevor
Load utility allows you to load one or more members, from data sets external to
CA Endevor
, directly into any stage that is defined within a
CA Endevor
environment. You do not need to reassemble or recompile your programs. And, you can date/time stamp--or footprint--all corresponding library members in your source, object, and load libraries as the members are loaded.
The Load utility JCL is provided on the installation tape, in member BC1JLOAD of the JCLLIB.
The actual load requests have already been generated, using the formats provided in Step 3 of the conversion job stream, and written to a data set. You need only to tailor the JCL and submit the job for execution.
Provide values for the following variables:
  • iprfx
    Highest-level qualifier used to assign data set names for installation files at your site.
  • iqual
    Second-level qualifier used to assign data set names for installation files at your site.
  • uprfx.uqual.INCL.SCLSTMTS
    The name of the data set that contains the load statements (output from phase 1 of the conversion process).
Load Utility Output
There are up to four reports produced as the Load utility executes. The reports you see depend on whether any Load requests contain syntax errors, data errors, or both. Reviewing these reports allows you to find problems and errors before the data set members are loaded into
CA Endevor
.
The following describes the report name and when the report is produced:
  • CA Endevor
    LOAD Execution Log
    Always
  • CA Endevor
    Data Validation Report
    Only when the requests contain invalid data
  • CA Endevor
    LOAD Execution Report
    Only when the requests contain no syntax errors or invalid data
  • CA Endevor
    LOAD Execution Summary
    Only when the requests contain no syntax errors or invalid data
Validate Phase
The third phase of the conversion process checks if the members have been loaded correctly loaded into the
CA Endevor
.
After you have run the Load utility, you should check to be sure that all members were loaded into
CA Endevor
correctly. Use the Member Validation Program to validate that all of the members in a
single
data set have been loaded and exist in a specific
CA Endevor
environment.
To achieve the best results, the Member Validation Program must be run immediately after you have loaded a data set's members into
CA Endevor
. The program produces a report that provides specific information about each member in the data set. The accuracy of the report can be affected by subsequent actions against the elements.
Member Validation Program
The Member Validation Program processes only one data set at a time. If you want to validate more than one data set, you need to execute the program once for each data set. The data set to be validated is known as the
source data set
, and is identified by the ENVDSN00 DD statement in the Member Validation Program execution JCL. This DD statement can refer to a partitioned data set, a CA Panvalet data set, or a CA Librarian data set. These are the only types of data sets supported by the program.
The Member Validation Program assumes that the
CA Endevor
element name is the same as the data set member name. The program does not support members that were renamed when placed into
CA Endevor
.
Return Codes (Member Validation Program)
The Member Validation Program passes the following return codes:
  • 0
    All members in the source data set were found in the
    CA Endevor
    environment specified.
  • 4
    One or more members were not found in the environment specified.
  • 12
    The Member Validation Program encountered an error.
The Member Validation Program execution JCL is provided on the install tape in member ENBRVDSN in the JCLLIB.
Member Validation Program JCL
The Member Validation Program requires that the following parameters and DD statements be coded:
  • 'ENBRVDSN
    environment_name
    '
    The
    CA Endevor
    environment that will be searched for members. If you do not code this parameter, or the value is invalid, you receive an error message.
    Specify an up to eight character, valid
    CA Endevor
    environment name.
    There are no characters between ENBRVDSN and
    environment_name
    .
  • CONLIB DD
    Standard JCL statement.
    Change IPRFX and IQUAL to the qualifiers you are using for your site.
  • ENVMSGS1
    The destination of the Member Validation Report. The DD statement usually allocates a SYSOUT data set.
    No tailoring required.
  • ENVDSN00
    The data set that is to be validated.
    Specify the name of a data set (
    source.dataset.name
    ) generated by the conversion job stream. The data set must be partitioned, CA Panvalet, or CA Librarian.
Member Validation Report
This section describes the Member Validation Report that is generated by the Member Validation Program. This report contains information about the members loaded into the
CA Endevor
.
The Member Validation Report classifies each member in the data set into one of three categories:
  • The member was not found in the
    CA Endevor
    environment.
  • The member was found as an element and the element was loaded into
    CA Endevor
    from the source data set.
  • The member was found as an element but the element was not loaded from the source data set.
The report is written to the ENVMSGS1 DD statement.
Multiple Occurrences of the Member
The Member Validation Program searches the entire inventory structure in both stages of the specified environment. Therefore, it is possible that multiple occurrences of the member will be found. For example, the same element may be a member of different systems or may be associated with different types.
The report displays every occurrence of the element. In most situations, only one of the elements is valid. The other elements will be marked with the following message:
Found . . . but not loaded from the source data set