Defaults Table C1DEFLTS

18.1
The Defaults Table contains global system information, such as
CA Endevor
options installed at your site,
CA Endevor
control data set names, and settings available for
CA Endevor
features.
Although all of the default parameters are set at system installation, you may need to change the Defaults Table if your site purchases a new
CA Endevor
product, your library names change, or you want to tailor the information entered by the system installer. The table comprises a set of "C1DEFLTS" macros which, when assembled and link-edited, are known collectively as the Defaults Table.
The Defaults Table must:
  • be assembled or compiled and linked with the RENT attribute
  • reside in an APF-authorized load library
If these requirements are not met, a U0078 ABEND occurs. The U0078 ABEND is accompanied by an eight-digit reason code, the first four digits of which indicate why the abend occurred:
ABEND=S000 U0078 REASON=00180000
C1DEFLTS was not found, or is missing from the APF load library.
ABEND=S000 U0078 REASON=001C0000
C1DEFLTS was not linked with the RENT attribute.
C1DEFLTS Macro
There are three occurrences of the C1DEFLTS macro:
  • TYPE=MAIN
    Defines site-specific information. It must be the first macro specified in the table source. Only one TYPE=MAIN macro can be specified.
  • TYPE=ENVRNMNT
    Defines environment information. You can have any number of these macros in the table, but you must have one macro for each environment in your configuration. TYPE=ENVRNMNT macros follow the TYPE=MAIN macro.
  • TYPE=END
    Specifies the end of the table definition. TYPE=END macros follow the last TYPE=ENVRNMNT macro.
Editing the Defaults Table
When you edit the C1DEFLTS macro, follow the following standard IBM rules:
  • Place all macro specifications between columns 2 and 71.
  • To continue across lines, place an
    X
    in position 72 and start the continuation card at position 16 of the next line. Leave at least one blank space between the end of one card (usually a comma) and the continuation character in position 72.
  • Include at least one space between the macro name-C1DEFLTS-and the first keyword parameter-TYPE.
  • Within each parameter specification, do not include any spaces. If you are using literal operands that include a space, enclose the operand in single quotes.
When editing the macros, pay special attention to the comma and continuation character (X) that follow all but the last parameter within each macro. If either of these is inadvertently deleted, the table assembles with a return code of zero, but problems result at
CA Endevor
execution.
Assembling the Defaults Table
After you edit the Defaults Table, you need to assemble and link-edit the table.
You can use an SMP/E USERMOD to assemble and link-edit C1DEFLTS after it has been customized. Alternatively, you can edit the sample JCL BC1JTABL to assemble and link source module C1DEFLTS outside of SMP/E. BC1JTABL is supplied in the installation library
iprfx.iqual.CSIQJCL
. This stores the defaults table in iprfx.iqual.CSIQAUTU as member C1DEFLTS.
TYPE=MAIN Macro
The TYPE=MAIN Macro defines site-specific information. It must be the first macro specified in the table source. Only one TYPE=MAIN macro can be specified.
The following information shows the TYPE=MAIN macro:
C1DEFLTS TYPE=MAIN, X ACCSTBL=, ACCESS SECURITY TABLE NAME X ACMROOT=, ACM INDEX ROOT DATA SET NAME X ACMXREF=, ACM INDEX XREF DATA SET NAME X ALOGDSN=, ACTION LOG DSN X APRVFLG=N, APPROVAL PROCESSING (Y/N) X ASCM=N, ACM CONTROL OPTION X AUTHTBLS=REQUIRED, REQUIRED|ALLOW|IGNORE X BATCHID=0, BATCH UID FROM JOBNAME/USER= X CA7CCINODE=, CA 7 ADDR SPACE NODE (CAICCI) X CA7JCLID=, CA 7 JCL DATASET INDEX NUMBER X CA7JCLLIB=, CA 7 JCL DATASET SYMBOIC INDEX X CA7JCLDSN=, CA7JCLID/CA7JCLLIB DSNAME X CIPODSN=, CCID VALIDATION DATASET NAME X CNFGTBL=ENDICNFG, CONFIGURATION TABLE NAME X COMPLISTWD=LIST, COMPONENT LISTING STRING ID X CUNAME='*** PUT YOUR COMPANY NAME HERE ***', (50 CHAR) X DB2=N, DB2 CONTROL OPTION X DESTCFGMBR=, PARMLIB DEST CONFIG MEMBER X DFCMBR=, DEFERRED FILE CREATION MEMBER X E2ELOGMBR=, END-2-END USS LOGGING MEMBER X EDITELM=N, EDIT ELEMENT DIALOG OPTION X ELMCATL='UPRFX.UQUAL.ELMCATL', E/MVS CATALOG X ELMCATE='UPRFX.UQUAL.ELMCATE', E/MVS CATALOG EINDEX X ESMTPTBL=ESMTPTBL, ENDEVOR SMTP TABLE NAME X ESSI=N, ESI CONTROL OPTION X EXITTBL=C1UEXITS, EXIT TABLE NAME X JRNLGRP=, PITR JOURNAL GROUP ID X LIBENV=, LIBRARIAN (LB), PANVALET (PV) X LIBENVP=N, LIBRARIAN/PANVALET OPTION X LIBRPGM=, LIBRARIAN BATCH PROGRAM NAME X LINESPP=60, LINES PER PAGE X MACDSN='iprfx.iqual.CSIQOPTN', E/MVS SOURCE LIBRARY X MFAAPPL=, MULTI FACTOR AUTHENTICATION X MIXEDFMT=, ALL|(CCID,COMMENT,DESCRIPTION) X MODHLI=, HLQ FOR TEMPORARY DATA SETS ) X OPTTBL=ENCOPTBL, OPTIONS TABLE NAME X PARMLIB=, ENDEVOR PARMLIB DATA SET NAME X PDM=N, PDM CONTROL OPTION X PKGDSN='UPRFX.PACKAGE.MASTER', PACKAGE DATASET X PKGTSO=N, FOREGROUND PACKAGE EXEC (Y/N) X PKGCSEC=N PKG CAST SECURITY CHECKING X PKGISEC=N PKG INSPECT SECURITY CHECKING X PKGCVAL=O, PKG COMPONENT VALIDATION Y/N/O X PKGSEC=APPROVER, APPROVER/ESI/MIGRATE X PRBLKSZ=0, BLKSZE PROC LISTING X PRLNKSZ=(896K,96K), LINKAGE SIZE FOR PROCS X PRLSTSZ=10, SIZE ALLOC FOR PROCS LISTINGS X PROC=N, PROCESSOR OPTION X RACFUID=, ALTERNATE ID USERID X RJCLROOT=, SHIP REMOTE JCL MODEL MBR ROOT X SITEID=0, ENDEVOR/MVS SITE IDENTIFIER X SMFPKGADM=N, SMF LOG PACKAGE ADMIN ACTIONS X SMFREC#=0, SMF RECORD NUMBER X SOFETCH=N, SIGNOUT UPON FETCH (Y/N) X SPFEDIT=SPFEDIT, DEFAULT PDS RESERVE X SPAWN=N, CONCURRENT ACTION PROCESSING X SPAWNCNT=, SPAWN COUNT X SPAWNMAX=, SPAWN MAXIMUM X SPAWNPROC=, SPAWN PROCESSOR NAME X SYMBOLTBL=, SITE-DEFINED SYMBOL TBL NAME X [email protected]=, REGRESSION ALERT NOTIFY (Y/N) X [email protected]=, SEVERITY ALERT LVL (I/W/C) X SYSIEWL=SYSIEWLP, DEFAULT PDS/LINK EDIT RESERVE X TYPESEQMBR=, ENDEVOR TYPE SEQ MBR X UIDLOC=(1,7), UID/JOBNAME START/LENGTH POS X VIOUNIT=TDISK, UNIT FOR VIO-ELIGIBLE ALLOC X WORKVOL=, VOL SER NUMBER FOR WRKUNIT X WRKUNIT=TDISK UNIT NAME FOR WORK SPACE
The following information defines each TYPE=MAIN parameter.
  • ACCSTBL
    The 1- to 8-character name of the Access Security Table used at your site. Enter a valid name.
    If you are using the ESI feature and leave this field blank, the Access Security Table name defaults to
    BC1TNEQU
  • ACMROOT
    The data set name of the VSAM file your site will use to store the name of each
    CA Endevor
    Element and all its related components. The recommended name is uprfx.uqual.ACMROOT.
    This data set is required if your site is licensed to use the ACM option and have ASCM=Y set in the C1DEFLTS.
  • ACMXREF
    The data set name of the VSAM file you will use to store the name of each component relationship. The recommended name is uprfx.uqual.ACMXREF.
    This data set is required if your site is licensed to use the ACM option and have ASCM=Y set in the C1DEFLTS.
  • ALOGDSN
    Specifies the name of a sequential data set to which
    CA Endevor
    writes admin action SMF records as they are written to SMF.  We recommend that you name the data set uprfx.uqual.ALOGDSN. This data set must be created with the following DCB information: DSORG=PS, LRECL=3000 or greater, and RECFM=V(B). ALOGDSN is only used if SMFENV=Y, which specifies that SMF admin action records are to be written for this Environment.
  • APRVFLG
    Specifies whether approval processing is enabled. Set this parameter to Y if approval processing is enabled.
    If you set this parameter to N, approval processing will not be active no matter what approver group relationships have been defined.
  • ASCM
    Specifies whether the
    CA Endevor
    Automated Configuration Manager (ACM) facility is enabled at your site. If your site is using ACM, specify Y; otherwise specify N.
  • AUTHTBLS
    The tables that are named in the ACCSTBL and EXITTBL parameters of C1DEFLTS TYPE=MAIN should be loaded from an APF-authorized load library. When a table is loaded from a library that is not APF-authorized, the AUTHTBLS setting determines the behavior of
    CA Endevor
    in the following ways:
    • REQUIRED
      (Default) Issues a message that specifies the table that is in error, and abends. This is the recommended setting.
    • ALLOW
      Issues a message, and continues processing.
    • IGNORE
      Continues processing without issuing a message.
  • BATCHID (Required entry)
    Specifies whether the
    CA Endevor
    user ID associated with a batch job should be determined by the JOBNAME or the USER parameter specified on the jobcard with the values:
    • 0
      (Default) Determined by JOBNAME
    • 1
      Determined by the USER parameter if specified, otherwise the userid of the submitter.
    • 2
      Determined by the USER parameter if specified, otherwise by the JOBNAME
  • CA7CCIDNODE
    Specifies the CAICCI node name where the CA 7 Workload Automation address space executes. If no name is specified, local mode is assumed.
  • CA7JCLID
    Provides
    CA Endevor
    with the CA 7 Workload Automation parameter information required by CA 7 Workload Automation to schedule JOB execution. Parameter values should be obtained from the CA 7 Workload Automation implementation. Mutually exclusive with CA7JCLLIB.
  • CA7JCLLIB
    Provides
    CA Endevor
    with the CA 7 Workload Automation parameter information required by CA 7 Workload Automation to schedule JOB execution. Parameter values should be obtained from the CA 7 Workload Automation implementation. Mutually exclusive with CA7JCLID.
  • CA7JCLDSN
    The data set name associated with CA7JCLID or CA7JCLLIB.
  • CIPODSN
    The data set name of the sequential file your site plans to use to store valid CCID values. The recommended name is uprfx.uqual.VALCCID. This data set is required if you want to use the CCID validation facility.
  • CNFGTBL
    Specifies the name of the Configuration Table. By default,
    CA Endevor
    uses the name, ENDICNFG.
  • COMPLISTWD=LIST
    Specifies the string value for identifying listing libraries. You can override this value on the SCL statement PRINT ELEMENT by using the optional clause COMPONENT LIST TEXT STRING. You can override this value on API PRINT ELEMENT requests using the request field ALPRE_RQ_LISTSTR.
  • CUNAME (Required entry)
    The up to 50 character name that describes your site. This name is used in report headings.
  • DB2
    Specifies whether the
    CA Endevor
    for DB2 application is enabled at your site. If your site is using
    CA Endevor
    for DB2, specify Y, otherwise N.
  • DESTCFGMBR
    Specifies the member name of the destination configuration member in PARMLIB. This member is used by the Post-Ship Script feature to define symbols that are unique by destination for the script files.
  • DFCMBR
    Specifies the member name of the deferred file creation member in the PARMLIB library. This member is used by the Deferred File Creation feature to create files (base, delta, source output, processor output) that were not predefined when an inventory location was defined to
    CA Endevor
    .
  • E2ELOGMBR
    Specifies the name of the End-to-End logging member in the PARMLIB library. This member is required to enable the End-to-End logging feature that can log Package actions, Element actions, or both. This feature is required  to integrate
    CA Endevor
    with CA Application Lifecycle.
  • EDITELM
    Specifies whether the
    CA Endevor
    Quick Edit Option is enabled at your site. If your site is using this feature, specify
    Y
    . Otherwise, enter
    N
    .
  • ELMCATL
    The 1-44 character data set name of the Element catalog VSAM file. The Element Catalog supports long Element names and boosts performance by reducing the volume of I/O operations.
  • ELMCATE
    The name of the Element catalog EINDEX VSAM file. If left blank, the name will default to the name specified for ELMCATL with a suffix of .EINDEX.
  • ESMTPTBL
    Specifies the name of the SMTP Table. By default,
    CA Endevor
    uses the name, ESMTPTBL.
  • ESSI
    Specifies whether the ESI facility is enabled at your site. If your site is using ESI, specify
    Y
    . Otherwise, enter
    N
    .
    Do not activate this option until all of the security rules are written and in place.
  • EXITTBL
    Specifies the name of the Exit Table. By default,
    CA Endevor
    uses the name, C1UEXITS.
  • JRNLGRP
    Specifies a CA L-Serv journal group ID which relates the package data set named in this macro to a specific set of L-Serv journal files. Enables journaling in the package control files and is required for the Point-in-Time Recovery (PITR) feature. The format is: (groupID,nnnn).
    • groupID
      The one- to eight-character Point-In-Time Recovery journal group ID associated with the package journal files.
    • nnnn
      The one- to four-character CA L-Serv journal group subsystem ID.
  • LIBENV
    This parameter serves two purposes depending upon the LIBENVP parameter in C1DEFLTS.
    • If LIBENVP=Y, then
      • LIBENV=PV specifies that CA Panvalet is installed;
      • LIBENV=LB specifies that CA Librarian is installed.
    • If LIBENVP=N (default), then the include member syntax is used by CONWRITE, by the Expand Include Utility, or by both as follows:
      • LIBENV=PV specifies that checks will be made for CA Panvalet include member syntax (++INCLUDE) or COBOL COPY statements,
      • LIBENV=LB specifies that checks will be made for CA Librarian include member syntax (-inc) or COBOL COPY statements
      • LIBENV=blank (default), no syntax checking or expanding will occur.
  • LIBENVP
    Specifies whether your site is using CA Librarian or CA Panvalet with
    CA Endevor
    . If your site is using one of these library management applications, specify
    Y
    . Otherwise,
    N
    .
  • LIBRPGM
    Applicable only if the LIBENV value is LB. This is the name of the CA Librarian load module for your site.
  • LINESPP
    The number of lines per printed page for output generated by
    CA Endevor
    . Default is
    60
    . Valid entries are 1-99.
  • MACDSN (Required entry)
    The data set name of the library containing the macros. This library was created during the
    CA Endevor
    installation procedure. The recommended name is iprfx.iqual.CSIQOPTN. The data set is used by many
    CA Endevor
    functions and is required.
  • MFAAPPL
    Specifies the SAF application name for Multi-Factor Authentication (MFA) support. Use any valid SAF application name to turn MFA support on. Using blanks or values other than valid SAF application names turns MFA support off, as does omitting the MFAAPPL parameter. For more information about MFA, see "Multi-Factor Authentication (MFA)".
  • MIXEDFMT
    Determines whether
    CA Endevor
    accepts mixed-case entries in CCID, COMMENT, and DESCRIPTION fields. Values are:
    • CCID
      Accept mixed case in CCID fields.
    • COMMENT
      Accept mixed-case in COMMENT fields.
    • DESCRIPTION
      Accept mixed-case in DESCRIPTION fields.
    • ALL
      Accept mixed-case in all three fields.
    • NONE
      Do not accept mixed-case in any field.
    Multiple values can be specified by enclosing the values in () and separating them by a comma. For example,
    =(CCID,COMMENT)
    .
  • MODHLI
    Specifies the prefix, other than SYSyyddd, that is assigned to a temporary data set, creating a pseudo-temporary data set. The value specified should be a high-level qualifier that all
    CA Endevor
    users are authorized to use when allocating, deleting, and opening files for output. If MODHLI is
    not specified
    in the Defaults Table, the effective name is:
    SYS
    yyddd
    .T
    hhmmss
    .RA0.
    jobname.nnnnnn
    MODHLI has the following uses:
    • This parameter applies to those temporary data sets that are allocated with DISP=MOD in any processor step. Regular temporary data sets, which are not DISP=MOD, use the standard z/OS temporary data set name. The modhli prefix appears as the first node of the data set name. The effective name generated is:
      modhli
      .D
      yyddd
      .T
      hhmmss
      .RA0.
      jobname
      .
      nnnnnn
      • modhli
        The value coded on the MODHLI parameter in the C1DEFLTS table.
      • D
        yyddd
        Julian date.
        If your site security package requires temporary data sets to follow IBM naming standards, then SYS is used instead of D, so that the node name is: SYS
        yyddd
      • T
        hhmmss
        Time in hours, minutes, and seconds.
      • RAO
        RA0 is used instead of RA000 to make room for the eight-byte MODHLI and the six-byte temporary data set name.
        If your site security package requires temporary data sets to follow IBM naming standards, then the effective name is: SYS
        yyddd
        .T
        hhmmss
        .RA000.
        ddname
        For more information about the temporary data sets, see the optional feature: DS_INTERNAL_TEMP in the ENCOPTBL table.
      • jobname
        Same value as jobname.
      • nnnnnn
        The temporary data set name &&nnnnnn without the &&.
    • This parameter is also used for any client program that accesses the API through Web Services, such as the Eclipse-Based UI, CA CMEW, or a user written client program.
      • If a MODLHI value is coded, your Security administrator must grant all user IDs access to all data sets with the MODHLI high-level qualifier (HLQ). This requirement applies to access under all security products including RACF, CA Top Secret, or CA ACF2.
        The reason for this requirement is as follows. For a client program to access the API, the user ID sent to CAICCI to spawn the pool of STCs and the user IDs that issue requests to Web Services must have read/write access to these data sets. To enable this, the MODHLI parameter causes the data set names to be built with this format:
        modhli
        .D
        yyddd
        .T
        hhmmss
        .STC
        nnnnn
        .
        ddname
        • STC
          nnnnn
          The job ID prefixed by STC.
        • ddname
          The unique qualifier for one of the nine API related files (APIMSGS, C1MSGS1, and so on).
      • If a MODLHI value is
        not
        coded, then security is not affected, because the temporary data sets names are built by the operating system with the standard temporary data set HLQ in the following format: SYSyyddd.Thhmmss.RA000.jobname.nnnnnn
      • If your site uses RACF with the RACF PROTECTALL enabled, specify a value for MODHLI. When using the Eclipse-Based UI, CA CMEW, or any other client program under RACF with the RACF PROTECTALL option activated, security violations are issued, unless MODHLI is coded. This occurs because the ID used to allocate the temporary files required by Web Services is different than the ID used to open the files. Specifically, the data sets are allocated under the context of the user ID provided on the CA Common Services Common Communications Interface (CAICCI) request to spawn the pool STCs. The open and write requests are issued under the context of the user ID signed on to the client program that is issuing requests through Web Services.
  • OPTTBL
    Specifies the name of the
    CA Endevor
    Options Table. By default,
    CA Endevor
    uses the name, ENCOPTBL.
  • PARMLIB
    Specifies the Parmlib data set name. This library can contain members that are required for other features. For more information about the C1DEFLTS table parameters that use the PARMLIB, see:
    • TYPESEQMBR, for the Type Sequencing feature.
    • DESTCFGMBR, for the Post-Ship Script feature.
    • E2ELOGMBR, for the End-to-end USS logging of Package actions function.
  • PDM
    Specifies whether the
    CA Endevor
    Parallel Development (PDM) facility is enabled at your site. If your site is using PDM, specify
    Y
    . Otherwise, enter
    N
    .
  • PKGDSN
    (Required entry if you are using packages) The data set name of the VSAM file your site will use to store package information. This library was created during the installation procedure. The recommended name is uprfx.uqual.PACKAGE.
    The data set is required if your site plans to use any of the package processing features.
    Use the same data set name for definition of and allocation of the package data set.
  • PKGTSO
    Specifies whether foreground package processing is allowed. Set this parameter to
    Y
    if foreground processing is allowed at your site. Otherwise, set the parameter to
    N
    .
    When a processor runs as part of a package, the PKGTSO flag overrides the foreground execution flag in the processor group. This means that if PKGTSO=
    Y
    , all processors in that package will execute, regardless if the value in the foreground execution field for the processor group.
  • PKGCSEC
    Specifies whether actions should incur a security check at package cast time. Set this parameter to
    Y
    to have each
    CA Endevor
    action checked during the package cast operation.
    If you set this parameter to
    N
    , no action security check is performed during the package cast operation.
  • PKGISEC
    Specifies whether actions should incur a security check at package inspect time. PKGISEC does not have to be defined. If omitted,
    CA Endevor
    uses the PKGCSEC value to determine whether security checks are done during the inspect action. Set this parameter to
    Y
    to have each
    CA Endevor
    action checked during the package inspect operation.
    If you set this parameter to
    N
    , no action security check is performed during the package inspect operation.
  • PKGCVAL
    Specifies whether component validation is required when packages are cast. Values are:
    • Y
      Component validation is required, no matter who is working with the package.
    • O
      Component validation is optional. Whether validation takes place is determined by the person working with the package.
  • PKGSEC
    Specifies whether users must be part of an approver group to cast, or execute, a package.
    • APPROVER
      Specifies that the site would like to restrict package actions to package approvers.
    • ESI
      Specifies that the site would like to control package options through an external security package such as CA ACF/2 for z/SO, CA Top Secret, and IBM RACF via the ESI interface.
    • MIGRATE
      Specifies that the site is in transition between Approver security and ESI security. Both will be checked.
      The approver security rules take precedence over ESI security rules. If the user is granted access to the package by the approver rules, ESI will not be invoked. ESI will be invoked only when the user does not belong to any approver groups associated with the package (If there are no approver groups associated with the package (this is true for ALL packages before they are CAST), no access restrictions apply.)
  • PRBLKSZ=0
    Specifies the blocksize to be used for temporary files when compiling processors. If you are on a version of z/OS that does not support BLKSIZE=0, specify the value for this parameter that is a multiple of 121.
  • PRLNKSZ=(256K,64K)
    Specifies the size parameter used by the linkage editor. When adding very large processors with many symbolics, this parameter may need to be increased. For example, use (384K,64K).
  • PRLSTSZ=10
    The value of PRLSTSZ is used for the primary and secondary space allocation parameters (in cylinders) for processor listings. The value of PRLSTSZ may need to be increased for very large processors.
  • PROC
    Specifies whether processors are enabled at your site. If your site is using processors, specify
    Y
    . Otherwise, enter
    N
    .
  • RACFUID
    The alternate user ID for data set authorization checking.
  • RJCLROOT
    Controls the choice of remote JCL generation. There are three choices:
    • RJCLROOT
      Not specified. Causes the job stream to be programmatically generated without the use of model members.
    • RJCLROOT=FCPY
      Specifies the job stream is generated through a set of model members beginning with the character string #RJFCPY, in order to build CA-PDSMAN FASTCOPY JCL for the remote copy and deletes.
    • RJCLROOT=ICPY
      Specifies the job stream is generated through a set of model members beginning with the character string #RJICPY. These members rebuild IEBCOPY and IDCAMS JCL statements.
  • SITEID (Required entry)
    The 1-character name that identifies your site. It is used internally to differentiate between sites. Default is
    0
    (zero).
    SITEID is an integral part of the
    CA Endevor
    footprint. Any changes to this parameter for existing
    CA Endevor
    installations will result in a footprint-compromised error for each Element within that installation's environments.
  • SMFPKGADM
    Specifies whether
    CA Endevor
    should write out SMF package admin action records. Set this parameter to
    Y
    if you want package admin action records written out. Otherwise, set the parameter to
    N
    . The default is
    N
    . If you set this parameter to
    Y
    , specify a value for the SMFREC# in the TYPE=MAIN macro. If you do not specify avlue for SMFREC#,
    CA Endevor
    ignores the SMFPKGADM parameter.
  • SMFREC#
    Specifies the SMF record number assigned to SMF records written by
    CA Endevor
    . Set this value to
    0
    (zero) until you implement the SMF option. The parameters controlling which records are actually written are SMFACT, SMFSEC, and SMFENV in the TYPE=ENVRNMT macro.
    • Valid values for SMFREC# are 128 through 255.
    • 0 disables SMF recording. Invalid values are 1 through 127, which are IBM reserved SMF Record Type values. Specifying an invalid value also disables SMF recording.
  • SOFETCH
    Specifies whether the Element that is fetched should be signed out to you, if not already signed out to someone else
    Y
    , or not signed out
    N
    .
    This value will come into play with Add (Fetch), Generate (Copyback), Move (Fetch), Transfer (Fetch), Search and Replace (Fetch) and Quick-Edit.
  • SPFEDIT
    The queue name used when
    CA Endevor
    issues an enqueue on a sequential file or partitioned data set (not RECFM=U). This may be a source library, object library, or other user library. Default is
    SPFEDIT
    .
    The resource name for the enqueue name is the data set name.
  • SPAWN
    Determines if the Concurrent Action Processing Feature is enabled. Allowable values are Y or N.
    N (default) - Specifies that concurrent action processing is disabled. Actions will be processed one at a time regardless of any other C1DEFLTS parameters or the presence of the EN$CAP or EN$CAPnn JCL DD cards on the job request JCL.
    Y - Specifies that Concurrent Action Processing is enabled. However, if SPAWNCNT=0 then concurrent action processing will not take place unless an EN$CAP
    nn
    DD card is present in the JCL and
    nn
    (number of servers to spawn) is greater than 2.
  • SPAWNCNT
    The number of action request regions allowed for a job. Allowable values are 0 and 2-99. The value must be less than or equal to the SPAWNMAX value.
    0 - Concurrent Action Processing is disabled. Actions are single threaded, regardless of the setting of SPAWN.
    2-nx - Specifies the maximum number of action request regions allowed per task. A value greater than zero is not allowed if SPAWN=N. This is the number of processors that are created if the EN$CAP DD card is present in the JCL.
    Note: If SPAWN=Y is specified, then the user can override a SPAWNCNT of 0 by using a EN$CAPnn DD card in the job request JCL. If the nn value in the EN$CAPnn JCL DD statement is 00, then Concurrent Action Processing will be disabled for the job.
  • SPAWNMAX
    The maximum number of action request regions allowed for a job. Allowable values are 2-99. Note that zero is valid if the SPAWN indicator is set to a value of N.
  • SPAWNPROC
    The one to eight-character name of the Concurrent Action Processing server. This name should be a CA CCI SERVICE definition service_name and a started task procedure name. A name is only required if the SPAWN indicator is set to a value of Y.
  • SYMBOLTBL
    Specifies the name of the symbolics table in use at your site if you are using site-defined symbolics.
    For more information, see Site Symbolics.
  • Specifies whether source synchronization is active at a site. Valid values are Y or N or blank. The default is: [email protected]=,
    A blank or a N specification deactivates Source synchronization.
  • When source is found out-of-sync with an instance of itself at a higher location (which is marked as a sync location) in the software lifecycle, log messages are written to the action log. This parameter determines the severity of these messages. An
    I
    specification will produce Informational out-of-sync log messages, a
    W
    produces Warning log messages and a
    C
    produces Caution log messages. The default is: [email protected]=,
    A blank specification will default to
    I
    .
  • SYSIEWL
    The queue name used when
    CA Endevor
    issues an enqueue on a partitioned data set defined with RECFM=U (for example, a load library). Default is
    SYSIEWLP
    .
    The resource name for the enqueue is the data set name.
  • TYPESEQMBR
    Specifies the name of the Type Sequence member, which enables Global Type Sequencing. The Type Sequence member defines the type sequence order in which Element actions are processed at your site, regardless of the action's inventory location. If you specify this parameter, also specify the Parmlib data set parameter. An empty Type Sequence member will force type sequencing by type name order.
  • UIDLOC
    Specifies which character positions of the
    CA Endevor
    userid will be compared against the Signout Userid value in the Master Control File to determine if the
    CA Endevor
    userid is the Element owner during Element Signout and Signout override checks in batch processing. The first number Specifies the starting position and the second number Specifies the number of characters to be compared. For example, to compare the first three characters of the userid against the first three characters in the Signout Userid in the Master Control File, specify UIDLOC=(1,3). Default is the first seven characters: UIDLOC=(1,7).
  • VIOUNIT (Required entry)
    The unit name for temporary disk data sets that are stored on a virtual I/O unit.
  • WORKVOL
    The volume serial number of the disk used to store temporary data sets.
  • WRKUNIT (Required entry)
    The unit name for temporary disk data sets that are
    not
    stored on a virtual I/O unit.
Selecting a BATCHID Option
When executing Element actions in batch (C1BM3000),
CA Endevor
uses the values specified for BATCHID and UIDLOC, in the TYPE=MAIN section of your C1DEFLTS table, to derive the value to be used as the
CA Endevor
userid.
  • BATCHID specifies whether the
    CA Endevor
    userid associated with a batch job will be determined by the JOBNAME, the USER parameter specified on the jobcard, or the userid of the submitter. One of the following values must be specified:
    • 0— determined by the JOBNAME
    • 1— determined by the USER parameter if specified, otherwise the userid of the submitter
    • 2— determined by the USER parameter if specified, otherwise by the JOBNAME
  • UIDLOC specifies the starting position and the number of characters in the jobname and Master Control File Signout Userid field comparison.  The default is the first seven characters UIDLOC=(1,7).
Example: BATCHID Option
In the following example, user PAND and user NDVR attempt to Retrieve an Element that is currently "owned" by user NDVR, and the field comparison mask for Signout processing is set at UIDLOC=(1,4). Neither user has the authority to use the "OVERRIDE SIGNOUT" option. The following table shows the results of their attempts, where  /Y or /N specifies whether the userid mask value used for the Element Signout ownership comparison has allowed (Y) or denied (N) the action.
NA in any table cell specifies not applicable.
JOBNAME
SUBMITTER
USER= *
BATCHID=0 **
BATCHID=1
BATCHID=2
ABCDJ
PAND
PAND
ABCD/N
PAND/N
PAND/N
ABCDJ
PAND
NA
ABCD/N
PAND/N
ABCD/N
ABCDJ
NDVR
NDVR
ABCD/N
NDVR/Y
NDVR/Y
ABCDJ
NDVR
NA
ABCD/N
NDVR/Y
ABCD/N
PANDJ
PAND
PAND
PAND/N
PAND/N
PAND/N
PANDJ
PAND
NA
PAND/N
PAND/N
PAND/N
PANDJ
NDVR
NDVR
PAND/N
NDVR/Y
NDVR/Y
PANDJ
NDVR
NA
PAND/N
NDVR/Y
PAND/N
NDVRJ
PAND
PAND
NDVR/Y **
PAND/N
PAND/N
NDVRJ
PAND
NA
NDVR/Y **
PAND/N
NDVR/Y **
NDVRJ
NDVR
NDVR
NDVR/Y
NDVR/Y
NDVR/Y
NDVRJ
NDVR
NA
NDVR/Y
NDVR/Y
NDVR/Y
Notes:
* Several security packages have an optional feature to automatically append the user=/password= parameters on the job card at job submission. If this is the case at your shop, then BATCHID=1 is recommended.
** Many sites have job submission exits that ensure the jobname matches the submitter's userid. If your site does not utilize this feature, it is strongly recommended you DO NOT USE BATCHID=0.
TYPE=ENVRNMNT Macro
The TYPE=ENVRNMNT macro defines environment information. You can have any number of these macros in the table, but you must have one macro for each environment in your configuration. The TYPE=ENVRNMNT macros follow the TYPE=MAIN macro.
The following is the TYPE=ENVRNMNT macro.
C1DEFLTS TYPE=ENVRNMNT, X ENDBACT=N, ENDEVOR DB ACTIVE FLAG X ENDBAVL=N, ENDEVOR DB OPTION AVAILABLE X ENTRYSTG#=1, ENTRY STAGE IS STAGE 1 X ENVNAME='MVSTEST', ENVIRONMENT NAME (8 CHAR) X ENVTITL='SAMPLE TEST ENVIRONMENT', TITLE (40 CHAR) X JRNLGRP=, PITR JOURNAL GROUP ID X NEXTENV=(MVSPROD,P), NEXT ENV/STG ID IN MAP (8,1) X SMFACT=N, SMF ELEM ACTION OPTION (Y/N) X SMFENV=N, SMF ADMIN ACTION OPTION (Y/N) X SMFSEC=N, SMF SECURITY OPTION (Y/N) X STG1ID='U', X STG1NME='UT', X STG1PSAS=N, STAGE 1 PROM STOP AT STG (Y/N) X STG1TTL='UNIT TEST', X STG1VSM='SPRFX.SQUALUT.MCF', X STG2ID='Q', X STG2NME='QA', X STG2PSAS=N, STAGE 2 PROM STOP AT STG (Y/N) X STG2TTL='QUALITY ASSURANCE', X STG2VSM='SPRFX.SQUALQA.MCF', X [email protected]=N REGRESSION ALERT START LOC C1DEFLTS TYPE=ENVRNMNT, X ENDBACT=N, ENDEVOR DB ACTIVE FLAG X ENDBAVL=N, ENDEVOR DB OPTION AVAILABLE X ENTRYSTG#=1, ENTRY STAGE IS STAGE 1 X ENVNAME='MVSPROD', ENVIRONMENT NAME (8 CHAR) X ENVTITL='SAMPLE PRODUCTION ENVIRONMENT', TITLE (40 CHAR)X JRNLGRP=, PITR JOURNAL GROUP ID X NEXTENV=, NEXT ENV/STG ID IN MAP (8,1) X SMFACT=N, SMF ELEM ACTION OPTION (Y/N) X SMFENV=N, SMF ADMIN ACTION OPTION (Y/N) X SMFSEC=N, SMF SECURITY OPTION (Y/N) X STG1ID='I', STAGE 1 IDENTIFIER (1 CHAR) X STG1NME='INT', STAGE 1 NAME (8 CHAR) X STG1PSAS=N, STAGE 1 PROM STOP AT STG (Y/N) X STG1TTL='INTEGRATION STAGE', STAGE 1 TITLE (20 CHAR) X STG1VSM='SPRFX.SQUALINT.MCF', STAGE 1 MCF (VSAM) X STG2ID='P', STAGE 2 IDENTIFIER (1 CHAR) X STG2NME='PRD', STAGE 2 NAME (8 CHAR) X STG2PSAS=N, STAGE 2 PROM STOP AT STG (Y/N) X STG2TTL='PRODUCTION STAGE', STAGE 2 TITLE (20 CHAR) X STG2VSM='SPRFX.SQUALPRD.MCF', STAGE 2 MCF (VSAM) X [email protected]=N REGRESSION ALERT START LOC
To specify more than one environment, copy this macro as many times as necessary.
If you are creating an environment map, specify the next environment in each definition. Make sure that you code them in the proper order; starting with the first environment and continuing to the last environment (ithat is, start with the top and work down).
The following shows an example for three environments:
C1DEFLTS TYPE=ENVRNMNT, X . . . [email protected]= C1DEFLTS TYPE=ENVRNMNT, X . . . [email protected]= C1DEFLTS TYPE=ENVRNMNT, X . . . [email protected]=
The following information defines each TYPE=ENVRNMNT macro.
  • ENDBACT ENDBAVL
    Parameters related to the
    CA Endevor
    to
    CA Endevor
    /DB for IDMS Bridge.
  • ENTRYSTG#
    Specifies the entry stage, either 1 or 2, for the environment. If this parameter is not defined, the entry stage defaults to 1.
  • ENVNAME (Required entry)
    The up to eight character name of the
    CA Endevor
    environment to which this macro applies. This value must be unique within this Defaults Table (that is, to this site). The name can include any of (but only) the following characters: A-Z, 0-9, @, #, $.
    ENVNAME is an integral part of the
    CA Endevor
    footprint. Any change to this parameter for existing z/OS environments will result in a footprint-compromised error for each Element within that environment.
  • ENVTITL (Required entry)
    The up to 40 character descriptive title for the environment.
  • JRNLGRP
    An L-Serv journal group ID which, when entered, relates the Master Control Files named in this macro to a specific set of L-Serv journal files. Use of this parameter enables journaling in the Master Control File base and delta libraries (VSAM and non-VSAM).
    The format is: (gggg,nnnn)
    • gggg
      The journal group ID associated with the MCF and delta journal files.
    • nnnn
      The journal group subsystem ID.
  • NEXTENV
    The next environment/stage location on the environment map. The format is: (
    environment name, stage id
    )
    • environment name
      The 1- to 8-character name of the next environment.
    • stage id
      The identifier (1 or 2) of the stage in that environment. If you do not provide a stage ID,
      CA Endevor
      defaults to STAGE id=1.
  • SMFACT
    Specifies whether
    CA Endevor
    should write out SMF Element action records. Set this parameter to
    Y
    if you want Element action records written out. Otherwise, set the parameter to
    N
    . Default is
    N
    . If you set this parameter to
    Y
    , specify a value for the SMFREC# in the TYPE=MAIN macro. If you do not specify SMFREC#,
    CA Endevor
    ignores the SMFACT parameter.
  • SMFENV
    Specifies whether
    CA Endevor
    should write out SMF admin action records. Set this parameter to
    Y
    if you want admin action records written out. Otherwise, set the parameter to
    N
    . Default is
    N
    . If you set this parameter to
    Y
    , specify a value for the SMFREC# in the TYPE=MAIN macro. If you do not specify SMFREC#,
    CA Endevor
    ignores the SMFENV parameter.
  • SMFSEC
    Specifies whether
    CA Endevor
    should write out SMF security records. Set this parameter to
    Y
    if you want security records written out. Otherwise, set the parameter to
    N
    . Default is
    N
    .
    If you set this parameter to
    Y
    , specify a value for the SMFREC# in the TYPE=MAIN macro. If you do not specify SMFREC#,
    CA Endevor
    ignores the SMFSEC parameter.
  • STG1ID (Required entry)
    The 1-character identifier for the first stage, used during processing to select (or identify) the stage you want. Commonly used identifiers are 1 or A. Default is
    1
    .
  • STG1NME (Required entry)
    The up to eight character name assigned to Stage 1 for this environment. The stage name must be unique across all environments within a site (that is, within the Defaults Table). The stage name can include any of (but only) the following characters: A-Z, 0-9, @, #, $.
    Some commonly used Stage 1 names are: PREPROD, QA, STAGE1ID, and TEST.
  • STG1PSAS
    This is a stage level parameter that, if set to Y, activates the stop-at-stage feature for promotion packages. You can activate this feature for one or both stages within the same environment. To activate this feature for a second stage, use STG2PSAS. You can also activate this feature in more than one environment (for example, in QA/1 and PRD/1).
    If you do not wish to activate this feature you can code “STG1PSAS=N”, or “STG1PSAS=”, or not code the parameter at all. The default is N.
  • STG1TTL (Required entry)
    The 1- to 20-character descriptive title for the first stage. This name is used on various panels and reports to describe this stage.
  • STG1VSM (Required entry)
    The Master Control File data set name for Stage 1, as defined during installation. The data set name defaults to: uprfx.uqual.STAGE1.
  • STG2ID (Required entry)
    The 1-character identifier for the second stage, used during processing to select (or identify) the stage you want. Commonly used identifiers are 2 or B. Default is
    2
    .
  • STG2NME (Required entry)
    The up to eight character name assigned to Stage 2 for this environment. The stage name must be unique across all environments within a site (that is, within the Defaults Table). The stage name can include any of (but only) the following characters: A-Z, 0-9, @, #, $
  • STG2PSAS
    This is a stage level parameter that, if set to Y, activates the stop-at-stage feature for promotion packages at a second stage. You can activate this feature for one or both stages within the same environment. To activate this feature for the first stage, use STG1PSAS. You can also activate this feature in more than one environment (for example, in QA/1 and PRD/1).
    If you do not wish to activate this feature you can code “STG2PSAS=N”, or “STG2PSAS=”, or not code the parameter at all. The default is N.
  • STG2TTL (Required entry)
    The 1- to 20-character descriptive title for the second stage. This name is used on various panels and reports to describe this stage.
  • STG2VSM (Required entry)
    The Master Control File data set name for Stage 2, as defined during installation. The data set name defaults to: uprfx.uqual.STAGE2.
  • Specifies whether the Environment, Stage location is a source synchronization location. If [email protected]=Y, when an action adds or moves an Element to this location, or to any location higher up the map, a sync check is performed. If an Element located lower in the map is not in sync with the new Element, a synchronization notification email is sent to the owner of the out-of-sync Element at the lower location. If more than one [email protected] is specified in C1DEFLTS, regardless of its specification ([email protected]=, [email protected]=N, or [email protected]=Y,) all [email protected] parameters after the first one in the map are ignored.
TYPE=END Macro
The TYPE=END macro specifies the end of the table definition. It follows the last TYPE=ENVRNMNT macro.
The TYPE=END macro is shown next:
C1DEFLTS TYPE=END
Do not change this macro.
Alternate Customization Tables
You can use the ENUXSITE exit to select an alternate Defaults Table (C1DEFLTS) based on a user ID or other criteria.
If your site has many different groups that use the same libraries, but each group uses a different C1DEFLTS table, using alternate customization table names can simplify group management.
You can identify the following tables within the C1DEFLTS Table:
  • Optional Features Table (ENCOPTBL)
  • Configuration Table (ENDICNFG)
  • SMTP EMAIL Table (ESMTPTBL)
  • User Exits Table (C1UEXITS)
By using the ENUXSITE exit, unique C1DEFLTS tables can identify the table names that are to be loaded enabling flexibility for administrators.
The ENUXSITE Program
ENUXSITE is an exit, called at
CA Endevor
initialization, that allows your site to identify the name of an alternate Defaults Table (C1DEFLTS) based on a user ID or other criteria. An alternate Defaults Table might be used as a mechanism to test a new configuration at your site. Or, you may want to provide a specific Defaults Table for a group of users based on particular installation criteria.
The alternate Defaults Table must exist before you implement the exit.
Additionally, the ENUXSITE program must:
  • be assembled or compiled and linked with the RENT attribute
    An S0C4 ABEND might occur if you execute an exit program that has been linked with the RENT attribute but with is not reentrant.
  • reside in an APF-authorized load library.
If these requirements are not met, a U0078 ABEND occurs. The U0078 ABEND is accompanied by an eight-digit reason code, the first four digits of which indicate why the abend occurred:
  • ABEND=S000 U0078 REASON=00140000
    ENUXSITE was not found, or is missing from the APF load library.
ENUXSITE Program Parameters
When
CA Endevor
initializes a session, it searches the APF-authorized library for a user-written program named ENUXSITE. If the program is found,
CA Endevor
passes to the exit, using standard linkage conventions, a single, 16-character data field. The first eight characters of the field contain the name C1DEFLTS. The remaining eight characters contain the user ID associated with the current
CA Endevor
session.
When running in batch, the value specified as the user ID is one of the following:
  • The job name specified on the jobcard.
  • The value specified on the USER= parameter of the jobcard. This value, if provided, takes precedence over use of the job name.
Using the ENUXSITE Program
Two ways exist to select an alternate Defaults Table:
  • Modify the parameter by changing the first eight characters to the name of the Defaults Table you want to use. ENUXSITE returns control to
    CA Endevor
    to load the named table and use it as the
    CA Endevor
    Defaults Table.
  • Use the z/OS LOAD service to load an alternate table. Use the IDENTIFY service to identify the table as the “C1DEFLTS.” The exit returns control to
    CA Endevor
    , leaving the 16-character parameter unmodified.
Creating an Alternate Defaults Table
To create an alternate Defaults Table, follow the instructions for creating the Defaults Table, but change the name C1DEFLTS to the name that you want to assign the alternate Defaults Table. Verify that the link-edit output member name--DD SYSLMOD--specifies the correct name.
Example: Use a Different Version of the Defaults Table
The following example shows a COBOL program written to allow USER1 to have a different version of the Defaults Table than other users. The name of USER1's Defaults Table is TABLE1.
000100 IDENTIFICATION DIVISION. 00000100 000200 PROGRAM-ID. ENUXSITE. 00000200 000300 ENVIRONMENT DIVISION. 00000300 000400 DATA DIVISION. 00000400 000500 LINKAGE SECTION. 00000500 000600 01 LS-PARM-FROM-ENDEVOR. 00000600 000700 05 LS-TABLE-NAME PIC X(8). 00000700 000800 05 LS-USER-ID PIC X(8). 00000800 000900 PROCEDURE DIVISION USING LS-PARM-FROM-ENDEVOR. 00000900 001000 IF LS-USER-ID = 'USER1 ' 00001000 001100 THEN MOVE 'TABLE1 ' TO LS-TABLE-NAME. 00001100 001200 GOBACK. 00001200
Maximum Number of Environments
The maximum number of environments that can be defined in a C1DEFLTS table is 999. As a best practice, avoid linking together an excessive number of environments in a map, for performance reasons.