Appendix A. MSI FDA Checklist
This checklist can help you design, create, and implement
Field Developed Applications that use the CA MICS-SAS
Interface.
Note: Read section 4.2 and all of Chapter 7 before creating
any FDAs. These sections contain information describing the
FDA generation process and the syntax of all CA MICS
Component Generator (MCG) statements.
___1. Name and Number the FDA (ccc and nnn)
Select the three-character name and unique identifying
number for your MSI FDA.
The FDA name CANNOT be MSI and should not conflict with
existing CA MICS or user FDA names. Use U or Z as
the first character to avoid conflicts with existing
and future CA MICS Data Integration Applications.
The FDA number can be any value from 150 through 190,
but must not be the same number used by a previously
generated FDA. If there is a concern about eventually
using most or all of the numbers in this range, one
should define multiple information areas within a user
component wherever it is possible.
___2. Identify the SAS Input data sets
Identify the SAS data sets that will feed your MSI FDA.
These must be specified on INPUTSAS or INPUTMODEL
statements in sharedprefix.MICS.GENLIB(cccGENIN). Run
a SAS PROC CONTENTS to get a listing of variables in
the SAS data sets. From this listing the names of
common data elements, sort sequences, and data element
types can be determined.
___3. Create Initial sharedprefix.MICS.GENLIB(cccGENIN)
___a. Copy sharedprefix.MICS.GENLIB(MSIGENIN) to
sharedprefix.MICS.GENLIB(cccGENIN). This member
will serve as a template to assist in the
definition of the new MSI FDA.
___b. You do not need to change or modify any cccGENIN
contents at this time. Just make sure the name
(cccGENIN) matches the name you selected for your
MSI FDA. For example, if you selected ZTQ as
your MSI FDA name in Step 1, the
sharedprefix.MICS.GENLIB member must be named
ZTQGENIN.
___4. Create sharedprefix.MICS.CNTL(cccCGEN)
___a. Edit sharedprefix.MICS.PARMS(JCLGENUC) so that it
contains the following:
cccCGEN
where ccc is the MSI FDA name you selected in
Step 1.
Submit the job in
sharedprefix.MICS.CNTL(JCLGENUC). Ensure that
there are no error messages in MICSLOG or
SYSTSPRT, that the MICSLOG contains the normal
termination message, BAS10999I, and that the job
completes with a condition code of zero.
___b. JCLGENUC creates a new cccCGEN member in
sharedprefix.MICS.CNTL. Edit cccCGEN and add a
JCL statement referencing each SAS library
containing SAS data sets used as input for this
MSI FDA.
Example: //libname1 DD DSN=sas.source.lib1,
// DISP=SHR
//libname2 DD DSN=sas.source.lib2,
// DISP=SHR
Note: In Step 5 you will define the files for
your MSI FDA. Each file will identify the source
SAS data sets used as input with the MSI
INPUTSAS or INPUTMODEL statements. You will need
to remember and use the same libnames that you
use for the JCL statements you add to cccCGEN in
this step.
___5. Update sharedprefix.MICS.GENLIB(cccGENIN)
In this step you update the cccGENIN member you created
in Step 3 with information that defines your MSI FDA.
___a. Edit sharedprefix.MICS.GENLIB(cccGENIN)
___b. Edit the COMP statement to specify the name (ccc)
and number (nnn) of the MSI FDA. You determined
the values for ccc and nnn in Step 1 above.
___c. Edit the AREA statement to specify the
information area name (iii) for the first set of
files. It is recommended that you begin the
information area name with U or Z to avoid
conflicts with existing CA MICS information area
names.
Update the AREA statement label to reflect the
contents of this information area.
___d. Edit the FILE statement to specify the file name
name (fff) for your first MSI FDA file.
Update the FILE statement label to reflect the
contents of this file.
___e. EDIT the INPUTSAS statement and update
libname.member to identify the SAS data set used
to create this file. Use the same libname that
you used when adding the JCL statement for this
SAS data library to cccCGEN in Step 4 above.
___f. Use MSI statements as described in Chapter 4 of
this guide to complete the file definition.
Standard data element definition statements can
also be used. See Section 4.2.4.3, MSI Definition
Statements and Section 4.2.4.4, Standard Data
Element Definition Statements.
___g. Repeat Steps d-f to define other files for this
information area. If an additional information
area is required, add a new AREA statement after
the last file definition, then code file
definition statements as described in Steps d-f.
*************************************************
* *
* NOTE: It is not necessary to define all *
* information areas and files at this time. *
* Additional information areas and files can be *
* defined during the GENFILE process. *
* *
*************************************************
___6. Run MCG SYNTAX Check
The syntax checking mode of the CA MICS Component
Generator (MCG) provides a quick method of testing for
syntax errors in cccGENIN. The entire syntax of the
cccGENIN is tested including sequence definitions and
dependencies, but the FDA is not integrated into the
CA MICS database nor is any code generated. Running a
GEN SYNTAX can help find errors in FDA definition
before any code is generated. A GEN SYNTAX can be run
any time a change is made to cccGENIN.
___a. Edit sharedprefix.MICS.GENLIB(cccGENIN).
___b. Change the ACCT option on the COMP statements to
NOACCT. For GEN SYNTAX processing, NOACCT must
be specified. Since the FDA has not been
previously defined, specifying ACCT will cause
the MSICGEN to fail. This option can be changed
to ACCT during the GENSHELL and GENFILES MCG
processes.
___c. Change the GEN statement to read GEN SYNTAX.
___d. Run the syntax check by submitting the job in
sharedprefix.MICS.CNTL(cccCGEN). Ensure that
there are no error messages in ISPLOG and
MICSLOG, that MICSLOG contains the normal
termination messages, BAS20999I, and that the Job
completes with a condition code of zero.
___e. If you encounter syntax checking errors, correct
sharedprefix.MICS.GENLIB(cccGENIN) and resubmit
the cccCGEN job.
___f. This process can be repeated as many times as
necessary.
___7. Run the MCG GENSHELL Process
The GENSHELL process creates all the modules necessary
to support a MSI FDA and defines the FDA to CA MICS.
Since the GENSHELL can only be run once, the FDA name
and number must be finalized at this time and cannot be
changed.
___a. Edit sharedprefix.MICS.GENLIB(cccGENIN) and
change GEN SYNTAX to GEN GENSHELL.
___b. Modify the COMP statement to specify the
ACCT/NOACCT option. It is recommended that the
ACCT option be specified on the COMP statement
whether or not User Defined Accounts are actually
used in the MSI FDA. This will make it easier to
add User Defined Account Codes if they are
required at a later date. The inclusion of
account codes is controlled by adding a
NAME @@ACCT 00 0 0 0 0 0
statement to the file definition and then
specifying @@ACCT in a SEQUENCE statement.
*************************************************
* *
* NOTE: It is not necessary to define all *
* information areas and files at this time. *
* Additional information areas and files can be *
* defined during the GENFILE process. However, *
* data dictionary shells are only created for *
* data elements defined in the GENSHELL *
* process. *
* *
*************************************************
___c. Do not create sharedprefix.MICS.PARMS(cccACCT) at
this time. Default
sharedprefix.MICS.PARMS(cccACCT) and (cccACRT)
members will be generated by the GENSHELL
process.
___d. Run the GENSHELL by submitting the job in
sharedprefix.MICS.CNTL(cccCGEN). Ensure that
there are no error messages in ISPLOG and
MICSLOG, that MICSLOG contains the normal
termination messages, BAS20999I, and that the job
completes with a condition code of zero.
___8. Run the GENFILES process.
At this point, the CA MICS Component Generator (MCG)
has created all the necessary component definition
modules for the new FDA. The GENFILES process is used
to activate the FDA and generate the modules required
to execute it.
___a. Edit sharedprefix.MICS.GENLIB(cccGENIN)
___b. If you do not need to make additional file or
information area updates at this time, go to
Step 8.c now.
To make file or information area updates now,
edit sharedprefix.MICS.GENLIB(cccGENIN) and code
the updates. Change the GEN statement to GEN
SYNTAX to check your modifications.
Run the GEN SYNTAX check by submitting the job in
sharedprefix.MICS.CNTL(cccCGEN). Ensure that
there are no error messages in ISPLOG and
MICSLOG, that MICSLOG contains the normal
termination messages, BAS20999I, and that the job
completes with a condition code of zero.
___c. Update sharedprefix.MICS.PARMS(cccACCT). You
must define at least one account field if you
specified ACCT on the COMP statement in step
7.b above.
___d. Edit sharedprefix.MICS.GENLIB(cccGENIN) and
change the GEN statement to GEN GENFILES.
Run the GEN GENFILES process by submitting the
job in sharedprefix.MICS.CNTL(cccCGEN). Ensure
that there are no error messages in ISPLOG and
MICSLOG, that MICSLOG contains the normal
termination messages, BAS20999I, and that the job
completes with a condition code of zero.
___e. To complete the installation of MSI FDA, refer to
section 3.8.2 (Adding a Product to an Existing
Database), or to section 3.8.3 (Adding a New
Product to a New Database Unit) in the PIOM.
For instructions concerning the coding of unit-
level parameters for the FDA, refer to Section
7.6 of this guide.
