A fix is available
APAR status
Closed as program error.
Error description
If the z/VM Directory Manager server (DirMaint) becomes very busy, the DirMaint call eventually can time out. The user may receive a SMAPI request number and the user makes a SMAPI call to check if the asynchronous operation is done. The SMAPI call checks certain fields in a DirMaint column and then checks to see if data came back. If no data is returned or data says the operation is finished, SMAPI returns an operation complete return and reason code; otherwise SMAPI returns an operation still running return and reason code.
Local fix
Problem summary
**************************************************************** * USERS AFFECTED: All users of Systems Management API (SMAPI) * * servers running with the Directory * * Maintenance (DirMaint) product are affected * * by this change. * **************************************************************** * PROBLEM DESCRIPTION: * **************************************************************** * RECOMMENDATION: APPLY PTF * **************************************************************** The DIRMAINT server could become busy enough that certain SMAPI calls can time out. SMAPI then checks to see if the asynchronous DIRMAINT call succeeded. Since the DIRMAINT call timed out, the response to SMAPI can be incorrect and cause other problems in the future.
Problem conclusion
The SMAPI changes here take advantage of changes introduced to DIRMAINT in APAR VM66232. DIRMAINT now associates a system name with each request number and requesting SMAPI server name. SMAPI has been updated to check the request number, the requesting server name, and the server's system name when checking for request completion. Refer to the VM66255 MEMO file for instructions on handling the updated VSMWORK1 SAMPPROF file in z/VM 6.4.0 only.
Temporary fix
Comments
APAR Information
APAR number
VM66255
Reported component name
VM CMS
Reported component ID
568411201
Reported release
640
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2019-02-12
Closed date
2019-02-22
Last modified date
2020-12-16
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
UM35430 UM35431
Modules/Macros
DMSSJDMC DMSSJQAO DMSWSLCK DMSWSPRO DMSWSSMP VM66255 VSMWORK1
Fix information
Fixed component name
VM CMS
Fixed component ID
568411201
Applicable component levels
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":"SG27M","label":"APARs - z\/VM environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"640","Line of Business":{"code":"LOB16","label":"Mainframe HW"}}]
Document Information
Modified date:
12 January 2021