SMF Recording

The SMF option records each action and each security violation that occurs during processing.
Endevor 18.1
The SMF option records each action and each security violation that occurs during
CA Endevor
processing.
3
Enable SMF Recording
SMF recording is done on an Environment-by-Environment basis, which means that you can selectively enable SMF recording for each of your Environments. The SMF option can write out the following SMF records:
  • Security records
    For each security violation, or each error that is returned from the security exit (exit 1).
  • Element Action records
    For each action executed, except for the following actions: Print, Display, Copy, and List. Element Action records are written out at the end of action processing.
  • Admin Action records
    For each administrative action executed, Admin Action records are written out at the end of action processing.
The administrator enables the SMF options in the Defaults table (C1DEFLTS). Per Environment, recording can be enabled for security records, element action records, and/or admin action records.
Follow these steps:
  1. Edit the SMFREC# parameter in the C1DEFLTS TYPE=MAIN macro to specify an SMF record number for your site.
    SMFREC#
    -- Specifies the SMF record number assigned to SMF records written by
    CA Endevor
    at this site. Default is 0, which disables SMF recording.
    Talk to a systems programmer at your site to ensure that you are collecting the SMF records related to the record number specified in the SMFREC# parameter. Recording records is controlled in SYS1.PARMLIB(SMFPRMxx).
  2. Edit the following parameters in the C1DEFLTS TYPE=ENVRNMNT:
    SMFACT
    -- Specifies whether to write SMF element action records for this Environment.
    Y
    --Writes element action records for the Environment.
    N
    --Does not write element action records for the Environment. Default is N.
    SMFENV
    -- Specifies whether to write SMF admin action records for this Environment.
    Y
    --Writes admin action records for the Environment.
    N
    --Does not write admin action records for the Environment. Default is N.
    SMFSEC
    --Specifies whether to write SMF security records for this Environment.
    Y
    --Writes security records for the Environment.
    N
    --Does not write security records for the Environment. Default is N.
  3. Reassemble and link C1DEFLTS to activate the modifications.
You can use the CSV utility to extract SMF record data corresponding to activity related to
CA Endevor
actions or to security violations recorded by
CA Endevor
. For more information, see Using the Comma-Separated Value (CSV) Utility.
Admin Action Monitoring
You can monitor administrative actions on Environment objects using SMF recording and real-time logging. With the logging feature, changes made by any administrator that might affect your software applications can be quickly tracked back to the individual who made the change. This capability enables tighter control over how your software applications are managed in
CA Endevor
. Previously, SMF recording was available only for security and element action activity.
Both admin action SMF recording and logging are turned on by Environment. Admin actions are recorded whether they are submitted using the Batch Environment Administration facility (Batch Admin) or using the foreground panels. Recordable administrative actions include Define, Update, and Delete actions that affect the following Environment objects:
  • The inventory structure objects, which include Systems, Subsystems, and Types.
  • Other objects that are associated to an Environment. These objects can include Approver groups, Approver group relations, Processor groups, and Processor symbols.
The logging feature is an optional extension of the SMF admin action recording option. The same information that is written to SMF is written to the log and it is written in the same format.
Activate Admin Action SMF Recording and Logging
SMF recording must be turned on as a prerequisite to activating admin action SMF recording and logging. To turn on SMF recording, ensure that SMFREC#=
n
in the Defaults table, C1DEFLTS, TYPE=MAIN macro to specify an SMF record number for your site. You can activate admin action SMF recording and logging for one or more Environments.
  • To activate admin action SCM recording for a specific environment
    -- set SMFENV=Y in the C1DEFLTS TYPE=ENVRNMNT macro.
  • To activate the admin action log feature
    -- create a log data set and specify the data set name as the value for the ALOGDSN parameter in the C1DEFLTS TYPE=MAIN macro. ALOGDSN specifies the name of the sequential data set to which
    CA Endevor
    writes Admin Action SMF records, in addition to writing them to SMF.  We recommended 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). Any Admin Action recorded to SMF will also be recorded in this log file. You cannot write Admin Action records to this log file unless you are also recording them to SMF.
  • To activate admin action SMF recording for packages
    -- set SMFPKGADM=Y in the C1DEFLTS TYPE=MAIN macro.
For more information about the C1DEFLTS table, see Defaults Table C1DEFLTS.
Each time the log data set is updated with an SMF admin activity record, the data set is dynamically allocated and opened, the activity record is added, and the data set is closed and unallocated. You may notice that allocation and unallocation messages are written to the JES system messages file each time the log data set is updated.
Record Formats
CA Endevor
uses several blocks to build the SMF security and action records, each comprising one or more DSECTs. All SMF DSECTs are supplied by the following macros in iprfx.iqual.CSIQOPTN: $SMFBKDS, $SMFHDDS, $SMFREC1, $SMFREC2, $SMFREC4.
Each SMF record output by
CA Endevor
starts with a standard SMF header block (DSECT $SMFHDDS), which contains fields required by SMF, and the Environment and user names for the Element being processed.
CA Endevor
records can be identified by the record type field in the header block (SMHRECTY), which is defined in the Defaults Table for each site. This field is the same for each
CA Endevor
SMF record, and identifies the records as being specific to
CA Endevor
.
Following the header block, each record has a data block that is specific to the record type:
  • DSECT $SMFREC1 for security records.
  • DSECT $SMFREC2 for element action records. For activity records, the $SMFREC2 block encompasses one or more action-specific blocks.
  • DSECT $SMFREC4 for admin action records. For admin action records, the $SMFREC4 block encompasses one or more admin action-specific blocks.
For more information about each DSECT used to format SMF records, see the "DSECT Descriptions" section of this article.
SMF Security Records
SMF security records include data specific to the security violation being reported. The data block for security records is written out using DSECT $SMFREC1. The combined format for SMF security records, is described using the following DSECTs:
  • $SMFHDDS
  • $SMFREC1
SMF Element Action Records
SMF Element action records include data specific to the action being reported, and applies to all actions except PRINT, DISPLAY, COPY, and LIST. Each element action record has one occurrence of the $SMFREC2 DSECT, and one or more action-specific blocks from the $SMFBKDS macro, as appropriate to the action. Each action-specific block has an action-block header (DSECT SM2BHDDS), and either the type 1, 2, 3, 4 or 5 action-block detail information, respectively DSECT SM2ENVDS, SM2LCGDS, SM2LPRDS, SM2REQDS or SM2ALTDS.
The combined format for SMF element action records, is described using the following DSECTs:
  • $SMFHDDS
  • $SMFREC2
  • SM2BHDDS action-block header
  • $SMFBKDS action-block detail (type n, includes up to five action blocks)
There are five different types of action-block detail information, each having a different format, or DSECT (within the $SMFBKDS DSECT). Each format applies to specific actions, described briefly as follows. Where two occurrences of a DSECT are used by an action, (2) follows the action name, below.
Action Block Detail Type #
DSECT Type
Actions
Description
1
Environment (SM2ENVDS)
Add (2)
Alter
Update (2)
Retrieve (2)
Generate (2)
Move (2)
Delete (2)
Transfer (2)
Archive (2)
Restore (2)
Information describing the Environment where the action took place: name of the Environment, site ID, and so on. Where two blocks are used, one represents the source Environment for the Element, while the other represents the target Environment.
2
Last Change (SM2LCGDS)
Add
Update
Generate
Move
Delete
Transfer
Restore
Information about the last processor executed: processor name, date and time of execution, etc. Used for actions that can invoke a processor.
3
Processor Info (SM2LPRDS)
Add
Update
Generate
Move
Delete
Transfer
Restore
Information about the last processor executed: processor name, date and time of execution, etc. Used for actions that can invoke a processor.
4
Request Parameter Info (SM2REQDS)
All actions
General information about the action: CCID, comments, and so forth.
5
Alter Info (SM2ALTDS)
Alter
Information specific to the Alter action: Before field value, after field value, and match (mask) value.
DSECT Descriptions
This section describes each of the DSECTs used to write out SMF action and security records. In cases where specific fields are not applicable for the current processing, alphabetic fields are space-filled and numeric fields are zero-filled.
SMF Header Block Field Descriptions
The header block, $SMFHDDS DSECT, is written at the beginning of each SMF record.
CA Endevor
security and action records can be identified by the record type field in the header, SMHRECTY, which has the same value in every
CA Endevor
SMF record. This value is defined in the Defaults Table (defaults to 230).
The following information describes the SMF header block fields:
  • SMHLEN
    Size of the (security or action) record, in bytes. This includes the size of the header block as well as the data block:
    • $SMFREC1- Security records
    • $SMFREC2 (including all element action-specific blocks)- element action records
    • $SMFREC4 (including all admin action-specific blocks)- admin action records
  • SMHSEGID
    Not used.
  • SMHSID
    Operating system against which the SMF record is written. Always X'02' with release 3.7.
  • SMHRECTY
    Number that identifies this SMF record as specific to
    CA Endevor
    . This number is defined to
    CA Endevor
    through the Defaults Table.
  • SMHTIME
    Time the SMF record was created (binary time of day in 100ths of a second-1 = .01 second).
  • SMHDATE
    Date the SMF record was created (packed yyddd).
  • SMHCPUID
    Number to identify the CPU model on which
    CA Endevor
    is running.
  • SMHHDLEN
    Size of the header block (DSECT $SMFHDDS), in bytes.
  • SMHC1VER
    Code that identifies the format of the SMF record.
    • SMH$RF00-This record was created by
      CA Endevor
      release 2.2 or a prior release.
    • SMH$RF01-This record was created by
      CA Endevor
      release 2.5 or a later release.
  • SMHCTLTY
    Code that identifies the next record format in the SMF record.
  • SMHCONT
    Not used.
  • SMHSEQ
    Not used.
  • SMHC1ENV
    Environment name associated with the current processing.
  • SMHUSER
    User ID associated with the current processing.
  • SMHSIZE
    Size of the $SMFHDDS DSECT.
Security Record Data Block Field Descriptions
The security record data block, $SMFREC1 DSECT, applies to security records and includes data specific to the security violation being reported.
The following information describes the fields in the security record data block:
  • SM1RECLN
    Size of this data block (DSECT $SMFREC1), in bytes.
  • SM1RECVN
    Version number. Identifies the
    CA Endevor
    release that created the record. Valid values are:
    • 1 -- The record was created by a release of
      CA Endevor
      prior to release 4.0.
    • 2 -- The record was created by
      CA Endevor
      release 4.0 or a later release.
  • SM1FUNC
    Number that identifies the current activity: generally the type of action.
  • SM1FUNNM
    Applicable if SM1FUNC references a
    CA Endevor
    action. Name of the current action (ADD, UPDATE, etc.).
  • SM1ERRCD
    The 4 characters that are used to construct the error code written to the
    CA Endevor
    Execution Report for the current action in the ECBMSGCD field. The error code is formatted as C1XNNNNS, where:
    • X-Describes the origin of the message.
    • NNNN-Defined by this field.
    • S-Severity code associated with the return code field, ECBRTCD, in DSECT $ECBDS.
  • SM1ERRLN
    Not used.
  • SM1ERMSG
    Error message associated with the current Element action for the ECBMSG field.
  • SM1SITE
    CA Endevor
    site ID, as defined to the Defaults Table.
  • SM1STGID
    Stage number for the current action request: 1 or 2.
  • SM1STGCD
    Applicable if SM1FUNC references a
    CA Endevor
    action. Stage ID for the current action request.
  • SM1IFUNC
    Action information that is used internally by
    CA Endevor
    .
  • SM1ENVM
    Environment name for the current processing.
  • SM1STAGE
    Applicable if SM1FUNC references a
    CA Endevor
    action. Stage name for the current action request.
  • SM1SYSTM
    Applicable if SM1FUNC references a
    CA Endevor
    action. System name for the current action.
  • SM1SUBSY
    Applicable if SM1FUNC references a
    CA Endevor
    action. Subsystem name for the current action.
  • SM1STYPE
    Applicable if SM1FUNC references a
    CA Endevor
    action. Element type for the current action.
  • SM1ELEMT
    (SM1RECVN version 1 records only) Applicable if SM1FUNC references a
    CA Endevor
    action. Name of the Element specified for the current action.
  • SM1EAOFF
    (SM1RECVN version 2 records only) Element area offset. When the offset is added to the beginning of the record's address, the resulting address points to an area with in the SM1BFAREA. The Element area is comprised of two adjacent components:
    • Two byte field containing the length
    • Element name
  • SM1DSNAM
    (SM1RECVN version 1 records only) Applicable for security violations that relate to ADD, UPDATE, RESTORE, ARCHIVE, and RETRIEVE action requests. Data set name associated with the external file used by the current action.
  • SM1FAOFF
    (SM1RECVN version 2 records only) File area offset. When the offset is added to the beginning of the record's address, the resulting address points to an area with in the SM1BFAREA. The file area is comprised of two adjacent components:
    • Two byte field containing the length
    • File name
    The file name may be a traditional file or an USS path name.
  • SM1DSMEM
    (SM1RECVN version 1 records only) Applicable for security violations that relate to ADD, UPDATE, RESTORE, ARCHIVE, and RETRIEVE action requests. Member name associated with the Element for which the current action applies, within the above data set. Applicable when the data set is a library.
  • SM1NAOFF
    (SM1RECVN version 2 records only) Name area offset. When the offset is added to the beginning of the record's address, the resulting address points to an area with in the SM1BFAREA. The name area consists of two adjacent components:
    • Two byte field containing the length
    • File name
    The name may be a member name or an USS file name.
  • SM1BSIZ
    Base size of the record.
  • SM1BFAREA
    (SM1RECVN version 2 records only) This is reserved record space containing the various areas such as Element, file and name.
  • SM1SIZ
    Size of the $SMFREC1 DSECT
Element Action Record Data Block Field Descriptions
The Element action record data block, $SMFREC2 DSECT, applies to Element action records and includes information specific to the action being reported. Depending on the action type, one or more action-specific blocks are incorporated at the end of this DSECT.
The following information describes the Element action record data block fields:
  • SM2RECLN
    Size of this data block (DSECT $SMFREC2), in bytes, including all action-specific blocks included at the end (DSECT $SMFBKDS).
  • SM2RECVN
    Version number to identify this data block ($SMFREC2). This value was updated to 2 for addition of the Alter block. Use the SM2$CURV label to detect that either the record is the current version (2) or the previous version of the SMF Element action record.
  • SM2FUNC
    Number that identifies the current Element action: generally the current type of action.
  • SM2FUNNM
    Applicable if SM2FUNC references a
    CA Endevor
    action. Name of the current action (ADD, UPDATE, and so forth).
  • SM2BLKS
    Count of action-specific blocks included at the end of this DSECT: 1-5.
  • SM2RECHD
    Size of this data block (DSECT $SMFREC2), in bytes, excluding the action-specific blocks (DSECT $SMFBKDS).
  • SM2IFUNC
    Action information that is used internally by
    CA Endevor
    .
  • SM2HDRLN
    Size of the $SMFREC2 DSECT, excluding the action-specific blocks
  • SM2SIZ
    Size of the $SMFREC2 DSECT, including all action-specific blocks incorporated at the end.
$SMFBKDS MACRO Action-Specific Blocks
The action-specific block applies for Element action records, and includes data specific to the action being reported. $SMFBKDS includes six DSECTs-one action-block header and five action-block detail DSECTs. These DSECTs are used in pairs, with each pair including a header and one type 1, 2, 3, 4 or 5 detail DSECT. The type of detailed information included can be identified through the SM2BTYP field in the header.
Action-Block Header Field Descriptions (SM2BHDDS)
The following information describes the fields in action-block header:
  • SM2BLEN
    Size of this action-specific block (action-block header, SM2BHDDS, plus the action-block detail DSECT), in bytes.
  • SM2BTYP
    Code that indicates the DSECT used to write out the action-block detail for this action- specific block:
  • SM2BVER
    Version number to identify this DSECT ($SMFBKDS). This should always be 1 except for the action block header.
  • SM2BFLG1
    Not used.
  • SM2BFLG2
    Not used.
  • SM2BHDR
    Size of the action-block header ($SM2BHDDS).
Environment Action-Block Detail Field Descriptions (SM2ENVDS)
The following information describes the Environment action-block detail fields:
  • SM2SITE
    CA Endevor
    site ID, as defined to the Defaults Table.
  • SM2STGCD
    Stage ID for the current action request.
  • SM2STGID
    Stage number for the current action request: 1 or 2.
  • SM2SRCHR
    Search and Replace utility flag.
  • SM2$ELEM
    Search and Replace utility action on an Element.
  • SM2$COMP
    Search and Replace utility action on an output component.
  • SM2VER
    Version number associated in the MCF with the Element for the action request.
  • SM2LVL
    Number to identify the current level of the Element for the current action request.
  • SM2STAGE
    Stage name for the current action request.
  • SM2SYSTM
    System name for the current action request.
  • SM2SUBSY
    Subsystem name for the current action request.
  • SM2STYPE
    Element type for the current action request.
  • SM2ELEMT
    (Version 1 Record Only) Name of the Element specified for the current action request.
  • SM2EAOFF
    (Version 2 Record Only) Element area offset. The Element name for the current action request is stored in the buffer area located near the end of the record. When the offset is added to the beginning of this record's address, the resulting address points to an area within SM2EAREA buffer space. The Element area is composed of two adjacent components:
    • Two-byte length field
    • Element name
  • SM2PRGRP
    Processor group name for the current action request.
  • SM2DSNAM
    (Version 1 Record Only) Applicable for ADD, UPDATE, RESTORE, ARCHIVE, and RETRIEVE action requests. Data set name associated with the external file used by the current action.
  • SM2FAOFF
    (Version 2 Record Only) File area offset. The file name for the current action request is stored in the buffer area located near the end of the record. When the offset is added to the beginning of this record's address, the resulting address points to an area within SM2EAREA buffer space. The file area is composed of two adjacent components:
    • Two-byte length field
    • Data set name
    The file name may be a traditional data set or an USS path name.
  • SM2DSMEM
    (Version 1 Record Only) Applicable for ADD, UPDATE, RESTORE, ARCHIVE, and RETRIEVE action requests. Member name associated with the Element for which the current action applies, within the above data set. Applicable when the data set is a library; blank otherwise.
  • SM2NAOFF
    (Version 2 Record Only) Name area offset. The member name for the current action request is stored in the buffer area located near the end of the record. When the offset is added to the beginning of this record's address, the resulting address points to an area within SM2EAREA buffer space. The name area is composed of two adjacent components:
    • Two-byte length field
    • Member name (PDS file) or file name (USS)
    If a member/file name is not applicable to the current action, the offset value is set to zero.
  • SM2EAREA
    (Version 2 Record Only) Space reserved in the record containing various data such as the Element, file and member name.
  • SM2ENVLN
    Size of the action-specific block (header and detail) if the action-block detail uses the Environment DSECT ($SM2ENVDS).
Last Change Action-Block Detail Field Descriptions (SM2LCGDS)
The following describes the Last Change action-block detail fields:
  • SM2CCOM
    Current-level comment for the Element.
  • SM2MLDTE
    Current-level date for the Element.
  • SM2MLTME
    Current-level time for the Element.
  • SM2LUSID
    Current-level user ID for the Element.
  • SM2MLACT
    Last action executed for the Element.
  • SM2MLTOT
    Count of source statements for the Element, as of the current level.
  • SM2LCHLN
    Size of the action-specific block (header and detail) if the action-block detail uses the Last Change DSECT ($SM2LCGDS).
Processor Information Action-Block Detail Field Descriptions (SM2LPRDS)
The following describes the Processor Information action-block detail fields:
  • SM2LPRON
    (Element) name of the processor last run for the Element.
  • SM2LPROD
    Processor date for the Element.
  • SM2LPROT
    Processor time for the Element.
  • SM2LPROU
    Processor user ID for the Element.
  • SM2LPHRC
    Processor return code for the Element.
  • SM2LPRC1
    CA Endevor
    return code for the Element.
  • SM2PRCLN
    Size of the action-specific block (header and detail) if the action-block detail uses the Processor Information DSECT ($SM2LPRDS).
Request Parameter Info Action-Block Detail Field Descriptions (SM2REQDS)
The following describes the Request Parameter Info action-block detail fields:
  • SM2RCCID
    CCID associated with the current action request.
  • SM2RCOMM
    Comments associated with the current action request.
  • SM2RFLAG
    Not used.
  • SM2RSISO
    Indicates whether the current action requested a signout override: Y (Yes) or N (No).
  • SM2RSICO
    Applicable for a RETRIEVE action. Indicates whether the current action specified copy-only: Y (Yes) or N (No).
  • SM2REXPN
    Applicable for a RETRIEVE action. Indicates whether the current action requested that INCLUDEs be expanded: Y (Yes) or N (No).
  • SM2ROVER
    Applicable for a RETRIEVE action. Indicates whether the current action requested an overwrite if a member by the same name exists already in the output library: Y (Yes) or N (No).
  • SM2RRTCD
    The return code associated with the current action request.
  • SM2RDEL
    Indicates whether the Element was deleted upon completion of the requested action: Y (Yes) or N (No). This value is X'40' if a delete does not apply for the current action.
  • SM2REQLN
    Size of the action-specific block (header and detail) if the action-block detail uses the Request Parameter Information DSECT ($SM2REQDS).
  • SM2REMCH
    Indicates whether the Validate action with the Element Master option was specified. Possible values are: Y (Yes) or N (No).
    This field is currently not in use and will not be populated.
  • SM2RSYCH
    Indicates whether the Validate action with the Synchronization option was specified. Possible values are: Y (Yes) or N (No).
    This field is currently not in use and will not be populated.
  • SM2RCMCH
    Indicates whether the Validate action with the Component Validation option was specified. Possible values are: Y (Yes) or N (No).
    This field is currently not in use and will not be populated.
  • SM2RTMSG
    Indicates whether the Validate action with the Terse option was specified. Possible values are: Y (Yes) or N (No).
  • SM2RAUTG
    Indicates whether the AUTOGEN Element option was specified on the ADD, UPDATE or GENERATE action. Possible values are: Y (Yes) or N (No). If the value of this field is Y, the value of the SM2AUTX field will be N.
  • SM2RAUTX
    Indicates whether this where-used Element was generated on behalf of a component Element. Possible values are: Y (Yes) or N (No). If the value of this field is Y, the value of the SM2AUTG field will be N.
  • SM2RNSRC
    Indicates whether the NOSOURCE action option was in effect for the Generate, Add, or Update action. Possible values are: Y (Yes) or N (No).
  • SM2RSPAN
    Indicates whether one of the Autogen Span options was specified on the Add, Update or Generate action. Possible values are: N (span none), A (span all), S (span Systems), B (span Subsystems).
  • SM2RXACT
    • Y
      Indicates that the Exact Match option is enabled for the Alter action.
    • N
      Indicates that the Exact Match option is not enabled for the Alter action.
Alter Action Information Block Field Descriptions (SM2ALTDS)
The following information describes the Alter action-block detail fields:
  • SM2AFLD
    Contains the field ID requested for an Alter action. An SMF record is created for each field requested in an Alter action, meaning that one Alter action can create several Alter SMF records.
    An SMF record is only created if the Alter action is performed and the Master Control File is updated. No SMF record is created in the following cirsumstances:
    Possible values are as follows:
    1 -- Indicates the Alter action requested the replacement of a Generate CCID value in the Master Control File.
    2 -- Indicates the Alter action requested the replacement of a Last Action CCID value in the Master Control File.
    3 -- Indicates the Alter action requested the replacement of a Retrieve CCID value in the Master Control File.
    4 -- Indicates the Alter action requested the replacement of a Description value in the Master Control File.
    5 -- Indicates the Alter action requested the replacement of a Processor Group value in the Master Control File.
    6 -- Indicates the Alter action requested the replacement of a Signout Userid value in the Master Control File.
    7 -- Indicates the Alter action requested the replacement of a User Data value in the Master Control File.
  • SM2AUPDT
    Indicates whether the Master Control File was updated. Valid values are Y or N:
    Y -- Indicates that the Master Control File record was updated.
    N -- Indicates that the Master Control File record was not updated.
  • SM2ADATA
    Label for the beginning of the variable Alter data area. For the Alter action data area, only one group of fields exists per record, the data area is redefined for each group of fields. These fields correspond to the Alter action field IDs, refer to SMA2FLD for field ID values.
    Generate CCID fields:
  • SM2ACCGB
    Value of the Generate CCID before the Alter action.
  • SM2ACCGA
    Value of the Generate CCID after the Alter action.
  • SM2ACCGM
    Mask value specified as the from-value for the Generate CCID.
  • Last Action CCID fields:
  • SM2ACCLB
    Value of the Last Action CCID before the Alter action.
  • SM2ACCLA
    Value of the Last Action CCID after the Alter action.
  • SM2ACCLM
    Mask value specified as the from-value for the Last Action CCID.
  • Retrieve CCID fields:
  • SM2ACCRB
    Value of the Retrieve CCID before the Alter action.
  • SM2ACCRA
    Value of the Retrieve CCID after the Alter action.
  • SM2ACCRM
    Mask value specified as the from-value for the Retrieve CCID.
  • Description fields:
  • SM2ADESB
    Value of the Description before the Alter action.
  • SM2ADESA
    Value of the Description after the Alter action.
  • SM2ADESM
    Mask value specified as the from-value for the Description.
  • Processor Group fields:
  • SM2APRGB
    Value of the Processor Group before the Alter action.
  • SM2APRGA
    Value of the Processor Group after the Alter action.
  • SM2APRGM
    Mask value specified as the from-value for the Processor Group.
  • Signout Userid fields:
  • SM2ASGNB
    Value of the Signout Userid before the Alter action.
  • SM2ASGNA
    Value of the Signout Userid after the Alter action.
  • SM2ASGNM
    Mask value specified as the from-value for the Signout Userid.
  • User Data fields:
  • SM2AUSRB
    Value of the User Data before the Alter action.
  • SM2AUSRA
    Value of the User Data after the Alter action.
  • SM2AUSRM
    Mask value specified as the from-value for the User Data.
  • SM2AUSR_FPOS
    From-position specified for the User Data.
  • SM2AUSR_FTXL
    Length of the mask value (from-value) text string for the User Data.
  • SM2AUSR_TPOS
    To-position specified for the User Data.
  • SM2AUSR_TLEN
    To length specified for the User Data.
  • SM2AUSR_TTXL
    Text length of the replacement value specified for the User Data.
  • SM2AUSR_TPAD
    Pad character specified for the User Data. This field is required if the “to” length (SM2AUSR_TLEN) is greater than the length of the replacement value (SM2AUSR_TTXL)
Admin Action Record Data Block Field Description
The admin action data block, $SMFREC4 DSECT, applies to admin action records and includes data specific to the admin action being reported, depending on the admin action.
The following information describes the admin action record data block fields.
  • SM4RECLN
    Size of this data block
  • SM4RECVN
    Version Number. Identifies the
    CA Endevor
    release that created the record. Valid values are:
    1 – The record was created by a release of
    CA Endevor
    prior to release 4.0
    2 – The record was created by
    CA Endevor
    release 4.0 or a later release.
  • SM4FUNC
    Number that identifies the current action:
    1 – DEFINE
    2 – UPDATE
    3 – DELETE
    4 – CLONE
  • SM4FUNNM
    Applicable if the target object of the current action is an inventory object identified by the SM4ACTN value. Name of the current action. Possible values are:
    DEFINE-- The inventory object was created.
    UPDATE-- The inventory object was updated.
    DELETE-- The inventory object was deleted.
    CLONE-- The inventory object was cloned. Only applies to Systems.
  • SM4ACTN
    The target inventory object of the current action. Possible values are:
    APPRGRP - Approver Group
    APPRREL - Approver Group Relation
    PROCGRP - Processor group
    PROCSYM - Processor Symbol
    SYSTEM - System
    SUBSYS - Subsytem
    TYPE - Type
    TYPEDSN - Type data set. Only applicable for the Update function performed from the
    CA Endevor
    foreground non-batch panels.
    DEST - Destination
    DSNMAP - Data Set Mapping Rule
    USSMAP - USS Mapping Rule
  • SM4SITE
    CA Endevor
    site ID, as defined to the Defaults Table.
  • SM4ENV
    Environment name for the current action.
  • SM4STGID
    Stage ID for the current action.
  • SM4STG#
    Stage number for the current action
  • SM4WRITR
    Indicates  where the SMF record was written from. Possible values are:
    E-- From the
    CA Endevor
    foreground panels.
    S-- From
    CA Endevor
    batch SCL processed requests.
  • SM4DATE
    Date the SMF record was created (YYYYMMDD)
  • SM4TIME
    Time the SMF record was created (HHMMSSTH)
  • SM4DSNAM
    SMF action target dataset
  • SM4DLEN
    Size of data block
  • SM4DATA
    Start of SMF admin action data
  • SM4HDSLN
    Size of $SMFREC4 header
Type
  • SM4_TYP_SYSTEM
    System name for the current request
  • SM4_TYP_TYPE
    Type name for the current request
  • SM4_TYP_NXT_TYP
    Next type name for the current request
  • SM4_TYP_DESC
    Description for the current request
  • SM4_TYP_DFLT_PG
    Default processor group definition for the current request
  • SM4_TYP_BASE
    Base library definition for the current request
  • SM4_TYP_DELTA
    Delta library definition for the current request
  • SM4_TYP_INCLUDE
    Include library definition for the current request
  • SM4_TYP_SOL
    Source output library definition for the current request
  • SM4_TYP_EXP_INC
    Do Not Expand | Expand includes in source output library definition for current request
  • SM4_TYP_DLT_FMT
    Element delta format definition for the current request
  • SM4_TYP_CMP_FMT
    Component delta format definition for the current request
  • SM4_TYP_COMPR
    Do Not Compress | Compress base definition for the current request
  • SM4_TYP_RGR_PCT
    Regression percentage threshold definition for the current request
  • SM4_TYP_RGR_SEV
    Regression severity definition for the current request
  • SM4_TYP_SRC_LNG
    Source element length definition for the current request
  • SM4_TYP_CMPR_FR
    Compare from column definition for the current request
  • SM4_TYP_CMPR_TO
    Compare to column definition for the current request
  • SM4_TYP_ELM_LVL
    Do Not Consolidate | Consolidate element levels definition for the current request
  • SM4_TYP_ELM_AT
    Consolidate element at level definition for the current request
  • SM4_TYP_ELM_NUM
    Number of element levels to consolidate definition for the current request
  • SM4_TYP_CMP_LVL
    Do Not Consolidate | Consolidate component levels definition for the current request
  • SM4_TYP_CMP_AT
    Consolidate component at level definition for the current request
  • SM4_TYP_CMP_NUM
    Number of component levels to consolidate definition for the current request
  • SM4_TYP_USS_RFM
    USS record delimiter definition for the current request
  • SM4_TYP_LANG
    Language definition for the current request
  • SM4_TYP_PL_LANG
    Panvalet | Librarian language definition for the current request
  • SM4_TYP_DAT_FMT
    Data format definition for the current request
  • SM4_TYP_ELM_RFM
    Element record format definition for the current request
  • SM4_TYP_FIL_EXT
    File extension definition for the current request
  • SM4_TYP_DSLN
    Type data length
  • SM4_TYP_DATAAREA
    Type data area
Type Data Set
  • SM4_DSN_SYSTEM
    System name for the current request
  • SM4_DSN_REC_ID
    Record ID of the data set name being updated for the current request
  • SM4_DSN_DSN_TYP
    Type of data set for the current request: PS/PO/??
  • SM4_DSN_DSN
    Data set Name as updated for the current request
  • SM4_DSN_DSLN
    Type Dataset data length
  • SM4_DSN_DATAAREA
    Type Dataset data area
Processor Group
  • SM4_PGR_SYSTEM
    System name for the current request
  • SM4_PGR_TYPE
    Type name for the current request
  • SM4_PGR_NAME
    Processor Group name for the current request
  • SM4_PGR_DESC
    Processor Group Description for the current request
  • SM4_PGR_NXT_PGR
    Next Processor Group name for the current request
  • SM4_PGR_OUT_TYP
    Processor Group Output Type for the current request
  • SM4_PGR_PMOVE
    Move Action Uses Generate/Move processor definition for the current request
  • SM4_PGR_PXFER
    Transfer Action Uses Generate/Move processor definition for the current request
  • SM4_PGR_GEN_PRO
    Generate Processor name for the current request
  • SM4_PGR_GEN_FG
    Generate Processor Foreground Execution definition for the current request
  • SM4_PGR_DEL_PRO
    Delete Processor name for the current request
  • SM4_PGR_DEL_FG
    Delete Processor Foreground Execution definition for the current request
  • SM4_PGR__MOV_PRO
    Move Processor name for the current request
  • SM4_PGR_MOV_FG
    Move Processor Foreground Execution definition for the current request
  • SM4_PGR_DSLN
    Processor Group data length
  • SM4_PGR_DATAAREA
    Processor Group data area
System
  • SM4_SYS_SYSTEM
    System name for the current request
  • SM4_SYS_DESC
    Description for the current request
  • SM4_SYS_NXT_SYS
    Next system name for the current request
  • SM4_SYS_COMM_RQ
    Comments Required definition for the current request
  • SM4_SYS_CCID_RQ
    CCID Required definition for the current request
  • SM4_SYS_SISO
    Signin/Signout definition for the current request
  • SM4_SYS_SO_DSN
    Signout Data Set Validation definition for the current request
  • SM4_SYS_ELM_JMP
    Element Jump Acknowledgment definition for the current request
  • SM4_SYS_DUP_ELM
    Duplicate Element Name Check definition for the current request
  • SM4_SYS_DUP_EML
    Duplicate Element Name Check Error Severity Level definition for the current request
  • SM4_SYS_DUP_OUT
    Duplicate Processor Output Type Check definition for the current request
  • SM4_SYS_DUP_OSB
    Duplicate Processor Output Type Check Across Subsystems definition for the current request
  • SM4_SYS_DUP_OML
    Duplicate Processor Output Type Check Error Severity Level definition for the current request
  • SM4_SYS_ELM_AGE
    Retain Element Level By Age definition for the current request
  • SM4_SYS_ELM_LVL
    Retain Element Level For
    nnn
    Months definition for the current request
  • SM4_SYS_CMP_AGE
    Retain Component Level By Age definition for the current request
  • SM4_SYS_CMP_LVL
    Retain Component Level For
    nnn
    Months definition for the current request
  • SM4_SYS_S1_LOAD
    Stage One Load Library definition for the current request
  • SM4_SYS_S1_LIST
    Stage One List Library definition for the current request
  • SM4_SYS_S2_LOAD
    Stage Two Load Library definition for the current request
  • SM4_SYS_S2_LIST
    Stage Two List Library definition for the current request
  • SM4_SYS_DSLN
    System data length
  • SM4_SYS_DATAAREA
    System data area
Subsystem
  • SM4_SBS_SYSTEM
    System name for the current request
  • SM4_SBS_SUBSYS
    Subsystem name for the current request
  • SM4_SBS_NXT_SBS
    Next subsystem name for the current request
  • SM4_SBS_DESC
    Description for the current request
  • SM4_SBS_EXC_OUT
    Do Not Exclude | Exclude Duplicate Processor Output Check definition for this request
  • SM4_SBS_DSLN
    Subsystem data length
  • SM4_SBS_DATAAREA
    Subsystem data area
Processor Symbol
  • SM4_PSY_SYSTEM
    System name for the current request
  • SM4_PSY_TYPE
    Type name for the current request
  • SM4_PSY_PG_NAME
    Processor Group name for the current request
  • SM4_PSY_PRO_NAM
    Processor name for the current request
  • SM4_PSY_PRO_TYP
    Processor Type for the current request: GEN/DEL/MOV
  • SM4_PSY_DFLT_OV
    Active symbol value for the current request: (D)efault or (O)verride
  • SM4_PSY_SYM_NAM
    Symbol name being updated for the current request
  • SM4_PSY_DEF_VAL
    Default symbol value for the current request
  • SM4_PSY_OVR_VAL
    Override symbol value for the current request
  • SM4_PSY_DSLN
    Processor Symbol data length
  • SM4_PSY_DATAAREA
    Processor Symbol data area
Approver Group
  • SM4_AGR_NAME
    Approver Group name for the current request
  • SM4_AGR_QUORUM
    The minimum number of approvals required for this approver group
  • SM4_AGR_GRP_DSQ
    Indicates whether this group is subject to the approver disqualification process      
  • SM4_AGR_DESC
    Approver Group description for the current request                  
  • SM4_AGR_USER
    Up to 16 approver user IDs for this Approver Group                   
  • SM4_AGR_USR_REQ
    Up to 16 flags indicating whether the approvers are required for approval for this Approver Group
  • SM4_AGR_DSLN
    Approver Group data length
  • SM4_AGR_DATAAREA
    Approver Group data area
Approver Group Relation
  • SM4_AGJ_SYSTEM
    System name that is being related to the specified Approver Group for the current request
  • SM4_AGJ_SUBSYS
    Subsystem name that is being related to the specified Approver Group for the current request
  • SM4_AGJ_TYPE
    Type name that is being related to the specified Approver Group for the current request
  • SM4_AGJ_STG#
    Stage number that is being related to the specified Approver Group for the current request
  • SM4_AGJ_REL_TYP
    Type of relation: (ST)ANDARD (EM)ERGENCY
  • SM4_AGJ_AGRNAME
    Approver Group that is being related to the specified inventory location
  • SM4_AGJ_DSLN
    Approver Group Relation data length
  • SM4_AGJ_DATAAREA
    Approver Group Relation data area
Shipment Destination
  • SM4_DST_DEST_ID
    Name of the destination you are creating or updating
  • SM4_DST_DESC
    Destination description for the current request
  • SM4_DST_XMIT_CD
    Transmission method that is to be used to ship the Package to the remote destination
  • SM4_DST_RMT_NOD
    Site name to which Package outputs are to be shipped
  • SM4_DST_COMPLEM
    Indicator whether or not data sets can be shipped along with Package shipments
  • SM4_DST_HST_PFX
    Prefix to be assigned to the staging data sets that are created at the host node
  • SM4_DST_HST_DSP
    Disposition of the host staging data sets after the Package shipment utility is complete
  • SM4_DST_HST_UNT
    Unit type on which the staging data set is allocated
  • SM4_DST_HST_VOL
    Volume on which the host staging data sets will be allocated
  • SM4_DST_RMT_PFX
    Prefix to be assigned to the staging data sets that are created at the remote node
  • SM4_DST_RMT_DSP
    Disposition of the remote staging data sets after the Package shipment utility is complete
  • SM4_DST_RMT_UNT
    Unit type on which the staging data set is allocated
  • SM4_DST_RMT_VOL
    Volume on which the remote staging data sets will be allocated
  • SM4_DST_IP_NAME
    Specifies the TCP/IP shipment destination address for a shipment performed using the XCOM transmission method
  • SM4_DST_IP_PORT
    Specifies the number within the IPNAME address
  • SM4_DST_HUSSPFX
    Prefix to the staging USS files that are created at the host node
  • SM4_DST_HUSSDSP
    Disposition of the USS host staging files after the Package shipment utility is complete
  • SM4_DST_RUSSPFX
    Prefix to the staging USS files that are created at the remote node
  • SM4_DST_RUSSDSP
    Disposition of the USS remote staging files after the Package shipment utility is complete
  • SM4_DST_RMT_JC1
    Specifies the JCL jobcard to be used at the remote site (part 1 of 4)
  • SM4_DST_RMT_JC2
    Specifies the JCL jobcard to be used at the remote site (part 2 of 4)
  • SM4_DST_RMT_JC3
    Specifies the JCL jobcard to be used at the remote site (part 3 of 4)
  • SM4_DST_RMT_JC4
    Specifies the JCL jobcard to be used at the remote site (part 4 of 4)
  • SM4_DST_DSLN
    Destination data length
  • SM4_DST_DATAAREA
    Destination data area
Shipment Mapping Rule
  • SM4_DMR_DEST
    Name of an existing Package shipment destination
  • SM4_DMR_DESC
    Description of data set mapping rule for the current request
  • SM4_DMR_HST_DSN
    Name or mask of the host data set name for the current request
  • SM4_DMR_HMBRCYL
    Approximate number of members that one cylinder might contain for data sets that map to the rule being created or updated
  • SM4_DMR_RMT_DSN
    Name or mask of the remote data set name for the current request
  • SM4_DMR_DSLN
    Shipment Mapping Rule data length
  • SM4_DMR_DATAAREA
    Shipment Mapping Rule data area
Shipment USS Mapping Rule
  • SM4_UMR_DEST
    Name of an existing Package shipment destination
  • SM4_ UMR _DESC
    Description of USS mapping rule for the current request
  • SM4_ UMR _HST_PTH
    Name or mask of the host path name for the current request
  • SM4_ UMR _RMT_PTH
    Name or mask of the remote path name for the current request
  • SM4_ UMR _DSLN
    Shipment USS Mapping Rule data length
  • SM4_ UMR _DATAAREA
    Shipment USS Mapping Rule data area
Clone System
  • SM4_CSY_SYSTEM
    System name being created by the current request
  • SM4_CSY_DESC
    Description for System being created by the current request
  • SM4_CSY_FRM_ENVFix
    Environment name for the System from which the new System is being cloned
  • SM4_CSY_FRM_SYS
    System name from which the new System is being cloned
  • SM4_CSY_INC_SBS
    Specifies whether subsystems should be included for the clone request
    Values:
    Y, N
  • SM4_CSY_INC_TYP
    Specifies whether Types should be included for the clone request
    Values:
    Y, N