7. PARAMETERS › 7.2 Record Selection Parameters and JCL

7.2 Record Selection Parameters and JCL

When you specify data selection on the parameter
specification panels, you also need to edit the file that
specifies the input data records to be included or excluded
for data transfer and the file that contains the JCL for
receiving data.


SELECT FILE PARAMETERS

The record selection parameters for each of the different
datatypes supported by the VM Data Transfer Program are kept
in separate files in CMS:

    o  The parameter file for Account data selection is
       ACCOUNT SELECT.

    o  The parameter file for CA VM:Account data selection is
       CAVMACT SELECT.

    o  The parameter file for VM Monitor data selection is
       MONXA SELECT.

    o  The parameter file for Network data selection is
       NETDATA SELECT.

    o  The parameter file for VSE/POWER data selection is
       POWER SELECT.

All statements in these files are optional.  If the file
contains only a comment or if the file is missing, the
defaults in the record selection routines are used.  See
Figures 3-1, 3-2, 3-3, 3-4, and 3-5 for the default
INCLUDE/EXCLUDE settings.  You cannot select records for
error recording data.

The minimum abbreviation for each parameter is the first
letter of the parameter.

Comments may be placed on parameter records following the
record identifier or other operands by coding an exclamation
point (!) followed by a blank.  When the exclamation point is
read, the record is no longer scanned for parameters and the
next record in the file is processed.

CODING PARAMETERS

SELECT files may contain the following parameters.  The
parameter keyword must begin in column 1.

    o EXCLUDE or X parameter
      The EXCLUDE parameter specifies which records should be
      excluded from the data transfer.  The synonym for
      EXCLUDE is X.  Use the format

        EXCLUDE rid rid ...
      or
        X       rid rid ...
      where rid is the record identifier.

    o INCLUDE or SELECT parameter

      The INCLUDE parameter specifies which records should be
      included in the data transfer.  The synonym for INCLUDE
      is SELECT.  Use the format

        INCLUDE rid rid ...
      or
        SELECT  rid rid ...
      where rid is the record identifier.

    o UNKNOWN parameter

      The UNKNOWN parameter specifies the disposition of
      record types that are unrecognized.  The acceptable
      values for action are SELECT and EXCLUDE.  These values
      may not be abbreviated.  The default is SELECT.  The
      only exception is for network data, whose default is
      EXCLUDE.  Use the format

        UNKNOWN action
      where action is SELECT or EXCLUDE.

    o * parameter

      An asterisk followed by a space in a parameter record
      indicates that the record contains only comments.  The
      * parameter can appear anywhere in the parameter file.
      Use the format

        * Comment
      where the asterisk is in column 1.

ADDITIONAL SELECT FILE DIRECTIVES

You can use the following SELECT file commands for Network
data:

    o SYSID

      The SYSID parameter specifies the value that should be
      placed in the SMF SYSID field of NetView records (types
      37 and 39) if the contents of that field are
      uninitialized (binary zero).  The FORCE option of this
      parameter indicates that the SMF SYSID field should
      always be set, even if it is initialized.  The minimum
      abbreviation for SYSID is SYS.  Use the format

        SYSID id
      or
        SYSID id FORCE

      where id is a one to four character value that is
      stored in the NetView and/or NET/MASTER record.

    o NETSPY

      The NETSPY parameter specifies the record type that
      NetSpy uses when it creates data records.  The default
      value is 150.

      The value you should code for the NETSPY parameter in
      your Network data SELECT file is the same value your
      NetSpy administrator specified to NetSpy on the LOGTYPE
      parameter of NetSpy's INITPRM file.  Use the format

        NETSPY nnn

      where nnn is the record number (in decimal).

JCL FILE NOTES

The JCL files can be edited from the parameter entry screen
for each data source.  There are considerations for coding
the JCL:

o Job card:  you must specify all job card parameters that
  are valid in your installation.  This includes security
  parameters such as GROUP and PASSWORD.  The precise setup
  can be provided by your VM and MVS system administrators.

o Tape Transfer:  If you are using tape to transfer data from
  VM to MVS, you may not require data receive JCL.  When the
  data is written to tape in uncompressed format, it is
  directly usable by the CA MICS VM and CMS Analyzer's DAY080
  step.  If you wish to copy the data to disk, use either
  VMTRCV or IEBGENER.  If you use VMTRCV to copy the tape
  data to disk or to decompress the data, use
  sharedprefix.MICS.CNTL(VMTRECVM) as a model for the JCL.

The sections that follow describe the individual record
identifiers and JCL.

    1 - Record Identifiers and JCL - Account Data
    2 - Record Identifiers and JCL - CA VM:Account
    3 - Record Identifiers and JCL - VM Monitor Data
    4 - Record Identifiers and JCL - Network Data
    5 - Record Identifiers and JCL - VSE/POWER Data
    6 - JCL - Error Recording Data