IBM Support

VM66879: Z/VM 7.4 VMSES: FIX PACK - FEATURE 01 FIX 01

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as unreproducible in next release.

Error description

  • This APAR comprises VMSES Feature Pack 01 Fix Pack 01 for
    z/VM 7.4.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED: All customers using z/VM Centralized Service *
    *                 Management (z/VM CSM) to manage z/VM system  *
    *                 service.                                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    ****************************************************************
    * RECOMMENDATION: APPLY PTF                                    *
    ****************************************************************
    This APAR contains updates to resolve multiple z/VM Centralized
    Service Management (CSM) errors or problems that impact the use
    of CSM commands and function.
    
    Among the problems and issues addressed are:
    
    * The CSM SERVMGR SYSTEM PUT2PROD function can incorrectly fail
      with message VMFCSY4046E.
    
      The command: SERVMGR SYSTEM PUT2PROD 730 system_name
    
      can incorrectly fail with message:
    
      VMFCSY4046E Error occurred during SYSTEM PUT2PROD processing;
                  completed work will be undone
    
      Running this same command again results in the SERVMGR SYSTEM
      PUT2PROD function completing successfully for the managed
      system.
    
    * When a SERVMGR SYSTEM DELETE 730 system_name command is issued
      message VMFCTL0390E may be reported:
    
       VMFCTL0390E HOST-CONNECT function error; invalid REXX
                   variable $CSMUTLFLIST.0 (2) for FILEGET operand
    
    * For a CSM principal system, for which its service is managed
      using CSM, either of the commands:
    
       - SERVMGR SRVLVL SEND 730 serv_lvl system_name
       - SERVMGR SYSTEM PUT2PROD 730 system_name
    
      may fail and need to be restarted more than once to complete.
    
    * When a SERVMGR SYSTEM QUERY 730 ALL command is issued, but no
      systems currently are being managed, a command failure is
      reported with message VMFCMG0002E issued:
    
       VMFCMG2195I SERVMGR SYS QUERY 730 ALL
       VMFCMG2760I SERVMGR processing started
       VMFCMG0002E File CSM SYSSTAT not found
       VMFCMG1965E Command SERVMGR failed with RC=28 when issued
                   with argument(s):  SYSTEM QUERY 730 ALL
       VMFCMG2760E SERVMGR processing completed unsuccessfully (RC=8
    
      It has been reported that these messages appear to convey a
      possible configuration error, and not the condition (no
      managed systems) that exists.  Issuance of a more accurate
      message for this situation has been requested.
    
    * Receipt of message:
    
      VMFCSY4005E File CSM SVCSTAT exists at file mode A
    
      when a SERVMGR INITIALIZE vrm command for a new z/VM level
      ('vrm' being 740) when the CSM root directory (VMPSFS:CSM730)
      for the existing z/VM 730 level already is accessed.
    
    * Receipt of message:
    
      VMFSRV1966W Command CPACCESS ended with RC=6706 when issued
                  with argument(s):  PMAINT CF0 MODE.ADDRCF0 SR
                  SYNCHRONOUS
    
      during SERVICE command processing.
    
    * Receipt of messages:
    
      VMFSIM2407E Input STEM DESCTQ. is not initialized Properly
      VMFSUT1965E Command VMFSIM QUERY failed with RC=12 when
                  issued with argument(s): VM SYSDESCT * STEM
                  DESCTQ. (STEM ODESCT.
    
      during VMFSUFTB command processing.
    

Problem conclusion

Temporary fix

Comments

  • The following changes are implemented by the updates provided
    via this APAR:
    
    Updates to the SERVMGR EXEC part:
    
    * Modifications to ensure the CSM root directory for a z/VM
      level ('vrm') is not accessed at filemode A when a SERVMGR
      INITIALIZE function is processed.  If a CSM root directory is
      accessed at filemode A when attempting to INITIALIZE a z/VM
      level, the code will LINK and ACCESS the MAINTCSM 191 disk R/W
      at filemode A instead.  Message VMF4041E also will be issued
      when the CSM root directory already exists for the 'vrm'
      specified on the SERVMGR INITIALIZE command.
    
    * Modifications that alter how existence validation of the
      CSM SYSSTAT and CSM SVCSTAT files are performed.  With these
      changes, when message VMFCMG0002E is issued for the case of a
      missing file, an applicable format of new message VMFCMG4049E
      issued:
    
       VMFCMG4049E No CSM managed systems can be identified
       VMFCMG4049E No CSM service levels can be identified
    
    Updates to the CSMSYSMT EXEC part:
    
     * Updates to handle the situation in which the $CSMUTL$
       HOST-CONNECT call for the PKG2PROD agent function is unable
       to retrieve (FTP) the CSMAGENT RTRVDATA file ($CSMFTPFERRS.0
       > 0).  In this case, the code now attempts to separately
       retrieve the CSMAGENT RTRVDATA file via an additional
       $CSMUTL$ HOST-CONNECT FILEGET function call.  If PKG2PROD
       CSMAGENT processing returns a nonzero return code and the
       CSMAGENT RTRVDATA file is not able to be reviewed, the
       message VMF4063E is issued.
    
     * Updates to ensure the correct file retrieval directive
       (FILEGET or FILEMGET) is specified when multiple managed
       system files are retrieved in the course of processing a
       SERVMGR SYSTEM DELETE command.  This change resolves the
       issue cited with the reporting of message VMFCTL0390E.
    
     * Additional changes have been made to erase an existing
       CSMP2P ACTIONRQ file in a pertinent 'MAINTCSM.sysname'
       subdirectory prior to processing a SERVMGR SYSTEM PUT2PROD
       command.  This has been done to avoid incorrectly issuing
       message VMFCSY4063I at command completion, which directs
       one to review the CSMP2P ACTIONRQ file (which if not
       newly created, will contain information that pertains
       to a prior command, and not that just processed).
    
    Updates to the CSMSRVMT EXEC part:
    
     * Updates to correct SFS directory and file clean up actions
       in multiple error handling paths have been implemented.
       These changes correct logic for instances when unexpected
       command errors are encountered during 'SERVMGR SRVLVL ADD
       csm_level' command processing.
    
    Updates to the $CSMUTL$ EXEC part:
    
     * The definition of a timing control variable
       (!g.7LCL_CMDtimeout) has been changed from a 5 minute value
       to a 30 minute value, to provide a longer interval for
       SERVMGR and CSMAGENT commands used for CSM -principal system-
       service management to complete without timing out.
    
    Updates to the $VMFUTL$ EXEC part:
    
     * Logic that creates the message log headers for various CSM
       and VMSES/E command logs has been updated to include CP QUERY
       TIME OFFSET response information in log headers produced for
       the SERVMGR and CSMAGENT commands.  This has been done for
       problem diagnostic purposes, to allow for better coordination
       and assessment of log information for principal and manage
       systems.
    
    Updates to the CSMAGENT command:
    
     * Corrections have been made to resolve value substitution
       errors when message VMFAGT4032E is produced.
    
    Updates to the SERVICE EXEC part:
    
     * Modifications for incorrect 'MODE.ADDRCF0' variable
       references, which produce this warning:
    
        VMFSRV1966W Command CPACCESS ended with RC=6706 when issued
                    with argument(s):  PMAINT CF0 MODE.ADDRCF0 SR
                    SYNCHRONOUS
    
       when CPACCESS commands are used to accommodate the placement
       of files on a System Parm disk (CF0) that already is CP
       accessed when SERVICE ENABLE commands, or more general
       SERVICE commands that require service environment variable
       updates, are used.
    
    Updates to the VMFSUFTB EXEC part:
    
     * Modifications for incorrect 'DESCTQ.' stem variable
       references, which produce this error:
    
        VMFSUT2760I VMFSUFTB processing started
        VMFSIM2407E Input STEM DESCTQ. is not initialized
                    properly
        VMFSUT1965E Command VMFSIM QUERY failed with RC=12 when
                    issued with argument(s): VM SYSDESCT * STEM
                    DESCTQ. (STEM ODESCT.
        VMFSUT2760I VMFSUFTB processing completed unsuccessfully
    
       when a program product is installed.
    
    Updated or new HELPMSG files are supplied for messages:
    
     - VMF4041E
     - VMF4049E
    
    ***START PUBLICATION CHANGE*************************************
    
    -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
    Publication Title: z/VM: Other Components Messages and Codes
    Release:      z/VM 7.4.0
    Order number: GC24-6300-74    GC24630074
    
    ----------------------------------------------------------------
    Chapter 3. System Messages
    Section: VMSES/E Messages
    
    Page(s): 371
    
    The 'User response' for message VMF4041E is updated, as follows:
    
     User response:
      Investigate why the SFS directory already exists.  For z/VM
      Centralized Service Management (z/VM CSM), the CSMvrm and
      CSMvrm.BASE directories will exist if the
      version/release/modification (vrm) environment has already
      been initialized.
    
    Page(s): 372
    
    The description for message VMF4049E is added, as follows:
    
     VMF4049E No CSM {managed systems|service levels} can be
              identified
    
     Explanation:
      A SERVMGR SYSTEM or SERVMGR SRVLVL command was issued that
      requires information about managed systems currently defined
      for the subject z/VM CSM group, or requires information about
      the service levels that pertain to the subject CMSvrm file
      space.  However, the respective CSM SYSSTAT or CSM SVCSTAT
      file that contains this information has been determined not to
      exist.
    
     System action:
      RC=8. Command processing stops.
    
     User response:
      Determine why the subject CSM file does not exist.  Check for
      a file that has been inadvertently renamed, or moved to some
      location other than the expected VMPSFS:CSMvrm. SFS
      directory.  After the missing CSM SYSSTAT or SVCSTAT file has
      been
    
    ***END PUBLICATION CHANGE***************************************
    

APAR Information

  • APAR number

    VM66879

  • Reported component name

    ESA VMSESS

  • Reported component ID

    568411209

  • Reported release

    740

  • Status

    CLOSED UR1

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2025-08-26

  • Closed date

    2025-12-19

  • Last modified date

    2026-01-17

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

    UM90580

Modules/Macros

  • $CSMUTL$ $VMFUTL$ CSMAGENT CSMSRVMT CSMSYSMT SERVICE  SERVMGR
    VMFSUFTB VMFUME   VMFUMEB  VMF4041E VMF4049E 7VMSES40
    

Publications Referenced
GC24630074    

Fix information

  • Fixed component name

    ESA VMSESS

  • Fixed component ID

    568411209

Applicable component levels

  • R740 PSY UM90580

       UP26/01/15 I 1000

Fix is available

  • Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.

[{"Business Unit":{"code":"BU011","label":"Systems - zSystems software"},"Product":{"code":"SG27M"},"Platform":[{"code":"PF054","label":"z Systems"}],"Version":"740","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]

Document Information

Modified date:
17 January 2026