APAR status
Closed as canceled.
Error description
This information apar was created as supplemental documentation for customers applying SPE apars PL74917 (MVS) or PN03135 (VSE). The ptf cover letter for this SPE states that after application of the ptf, the Disoss DSVAPIQ and DSVSOCB datasets should be deleted, redefined and reinitialized. If the customer cannot perform this action, due to concerns about losing APIQ data, or due to the fact that API users must re-sign on to Disoss before receiving new mail after reorging these datasets, an alternative method exists which may be less disruptive. The customer may use the CICS transaction CECI, or his own user-written program to make the necessary changes to the DSVAPIQ dataset. The only change needed is to modify the DSVAPIQ status records. At offset x'10', the 'S' (x'E2') should be changed to 'A' (x'C1') for each API user's status record. The layout of the APIQ status record can be found in the Disoss Application Progamming Manual SC30-3096-7 on page 51. After making this modification, the customer should ensure that the APIQ records remain in KSDS sequence....If using CECI, this will be done automatically. Additionally, if the APIQ status records are modified using this procedure, the DSVSOCB dataset does not need to be reallocated. If this SPE is applied without making any of the recommended changes to the DSVAPIQ, the following symptoms may be noticed: 1. If mail is sent to a PS/CICS or OV/MVS user who has not signed on to Disoss since the ptf was applied, transaction DMDD may abend with abendu5015. Message DMDP081S with API RC=2 will be issued. This abend will be resolved after the user re-signs on to Disoss for the first time after ptf application. 2. After application of the ptf, and after a user re-signs on to Disoss, there may be 2 status records (1 'S' record, and 1 'A' record) in the dataset for this user. This will cause no harm, but in order to realize the performance benefit provided by the ptf, the 'S' record should be deleted as soon as is practical.
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
APAR Information
APAR number
II05826
Reported component name
PB LIB INFO ITE
Reported component ID
INFOPBLIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1992-03-12
Closed date
1992-10-05
Last modified date
1992-10-05
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Fix information
Applicable component levels
[{"Business Unit":{"code":null,"label":null},"Product":{"code":"SG19O","label":"APARs - MVS environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEPEK","label":"Db2 for z\/OS"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB10","label":"Data and AI"}}]
Document Information
Modified date:
13 December 2020