APAR status
Closed as canceled.
Error description
May seem CF Devices changed even when the IODF SOURCE and Target do not change anything regarding these CF's. Msg's would show something like this; IOS500I ACTIVATE RESULTS 030 TEST DETECTED CONDITIONS WHICH WOULD RESULT IN ACTIVATE FAILURE REASON=0381,CANNOT DELETE COUPLING FACILITY CU FFE1................... DESCTEXT=COUPLING FACILITY IS STILL ACTIVE......................... COMPID=SCIXL NOTE = 0100,SOFTWARE-ONLY CHANGE COMPID=SC1C3 NOTE = 0108,H/W AND S/W CONFIGURATION DEFINITIONS WILL BE BACK in SYNC. . The reason for this is that IOSVCMIN which calls the XCF routing. This routine will save the CCB IF it causes the software and hardware configuration to get out of sync. When the software and hardware configuration get back in sync XCF is then notified with the saved CCB's. . CMVC item has been opened to IOS to add a ctrace entry for the saved CCB. **************************************************************** NOTE: If you are receiving this message and this APAR does not describe the situation, ie. This is an Activate Test or Activate w/out SOFT then most likely a CF definition (CHPID, Control Unit or Device) in the TARGET IODF has changed. This may occur if the CF was disconnected and reconnected or if the CHPIDs to the CF were removed and added back in a different order by the user during an HCD session. Run the HCD Compare report AND review the CF connectivity Control Unit and Device numbers to poinpoint the changes Once identified, the target IODF should be changed to reflect the correct CU and Device numbers if the changes were not deliberate. ****************************************************************
Local fix
Activate the configuration SOFT in the n-1 images and then HARD in the last.
Problem summary
Problem conclusion
Temporary fix
Comments
info apar
APAR Information
APAR number
II14358
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt
Submitted date
2008-01-25
Closed date
2008-01-30
Last modified date
2012-01-21
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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SG19N","label":"APARs - OS\/390 environment"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"001","Edition":"","Line of Business":{"code":"","label":""}},{"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":"BU054","label":"Systems w\/TPS"},"Product":{"code":"SSSN3L","label":"z\/OS Communications Server"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"001","Edition":"","Line of Business":{"code":"LOB35","label":"Mainframe SW"}}]
Document Information
Modified date:
21 January 2012