Prerequisites for z/OSMF

The prerequisites you require to run IBM z/OS Management Facility (z/OSMF) with IBM MQ

The IBM MQ workflows shipped in Version 9.1.0 exploit new function in z/OSMF, which is provided through APARs on both z/OS Version 2.1 and Version 2.2. More details are provided in the following text.

  1. We have installed and configured IBM z/OS Management Facility Version 2.2 correctly. If we are running with security enabled, ensure that all security settings as documented by z/OSMF have been configured.
  2. We have installed the following APARs for:

      z/OS Version 2.1

      • PI71068
      • PI71079
      • PI71082
      • PI71084
      • OA50130

      z/OS Version 2.2

      • PI70526
      • PI70521
      • PI70527
      • PI67839
      • PI70767
      • PI46315
      • OA49081
      • OA49802
      • OA50130

  3. The z/OSMF angel (if required) and server processes have been configured.
  4. The z/OS Cloud environment has been configured (as briefly discussed above and documented by z/OSMF)
  5. IBM MQ for z/OS Version 9.0.1 has been installed and the product load libraries are available.
  6. The following IBM MQ queue manager customization tasks have been performed:

    Task Description
    1 Identify the z/OS system parameters
    2 APF authorize the IBM MQ load libraries
    3 Update the z/OS link list and LPA
    4 Update the z/OS program properties table
  7. The sample workflows and associated files are installed in a suitable UNIX System Services for z/OS (USS) directory.
  8. The ‘/tmp' USS directory is available, as the provision.xml workflow might create a temporary file in this directory. If a file is created, the workflow, in general, deletes the file after use.
  9. The deprovision.xml file has steps in it that invoke the CSQ4ZWS1.rexx and CSQ4ZWS2.rexx REXX execs. These execs wait for the queue manager and channel initiator subsystems to stop; the execs invoke the USS 'SLEEP' command as a system call. Depending on your USS configuration, you might find that the 'SLEEP' command does not work as coded. If, during processing you encounter an error which indicates that the 'SLEEP' command cannot be found, we can try replacing the following lines in execs CSQ4ZWS1.rexx and CSQ4ZWS2.rexx:
    CALL SYSCALLS('ON')		     /* Enable USS calls    */
ADDRESS SYSCALL
"SLEEP" 10                           /* Sleep for 10 seconds */
CALL SYSCALLS 'OFF'		     /* Disable USS calls    */
    with
    'sleep' 10

    Then, issue the Open MVS (OMVS) env command to check your PATH environment variable setting. Ensure that the directory which contains the sleep command is defined to the PATH. Note that the sleep command is typically found in the /bin directory.

  10. Ensure that z/OSMF has been started.

    Both the angel and server z/OSMF processes must be started and the z/OSMF Web User Interface (WUI) be up and running. For further details, see Liberty profile: Process types on z/OS.

    Even if you intend to drive the workflows using the REST API, the z/OSMF WUI needs to be started. The z/OSMF WUI can be useful for monitoring the creation and execution of workflows.

Parent topic: Use IBM z/OSMF to automate IBM MQ


Related concepts