A fix is available
APAR status
Closed as new function.
Error description
When a client has many IMS systems ( >100 ) both native and SQ, in order to guarantee business continuity they have to be able to move IMS across z/OS and LPAR's in case of z/OS failure, LPAR failure or even for workload balancing (close an LPAR and move IMS subsystems and QCF onto other z/OS systems). Under this basic requirement IMS QCF is implemented, but due to strict naming conventions for COMMIT, UNCOMMIT and NOTPARMS datasets (where MVSNAME is a must), clients are not able to respect it. Currently, IMS QCF requires the naming conventions to be as follows: ovflhlq.MVSNAME.IMSID.NOTPARMS ovflhlq.MVSNAME.IMSID.COMMIT ovflhlq.MVSNAME.IMSID.UNCOMMIT whereas MVSNAME is the second level HLQ. This restriction doesn't allow for the movement of IMS's and QCF's across a z/OS LPAR. This enhancement will remove MVSNAME as an HLQ restriction for the dataset allocation. This enhancement is based off of RFE 81642.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: Users of QCF 3.2, that will move IMSs * * across z/OS and LPARs. * **************************************************************** * PROBLEM DESCRIPTION: If customer has more IMS's systems * * (both native and SQ), In order to * * guarantee business continuity they are * * now able to move IMS across z/OS and * * LPAR in case of z/OS failure, LPAR * * failure or even for workload balancing * * (close an LPAR and move IMS subsystems * * and QCF on others with different z/OS). * * MVSNAME.IMSID.NOTPARMS * **************************************************************** * RECOMMENDATION: Install the APAR, and set the preferences * * for NOTPARMS, COMMIT and UNCOMMIT data set * * names. Create the common data sets, if you * * choose that they do not have the MVSNAME * * and/or IMSID as middle level qualifiers. * **************************************************************** Allow for COMMIT, UNCOMMIT, and NOTPARMS data sets to not include MVSNAME and IMSID names
Problem conclusion
Temporary fix
Comments
Install the APAR, set the preferences and create the new data sets, that do not have the MVSNAME and/or IMSID as middle level qualifiers.
APAR Information
APAR number
PI87887
Reported component name
IMS QUEUE CNTL
Reported component ID
5697E9900
Reported release
320
Status
CLOSED UR1
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2017-09-25
Closed date
2019-03-11
Last modified date
2019-04-02
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UI61761
Modules/Macros
IQCF22 IQCH34V IQCI00 IQCP0000 IQCP0010 IQCP0100 IQCP34V IQCUCHF
Fix information
Fixed component name
IMS QUEUE CNTL
Fixed component ID
5697E9900
Applicable component levels
R320 PSY UI61761
UP19/03/13 P F903
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19M","label":"APARs - z\/OS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSCX8A6","label":"IMS Queue Control Facility"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"320","Edition":"","Line of Business":{"code":"","label":""}}]
Document Information
Modified date:
02 April 2019