APAR status
Closed as canceled.
Error description
. See, also, II11069 and OW45020. . *************************************************************** * If the problem persists after excluding type19 records for * * SUBSYS STC, check that SMCA+7C points to IEEMB838. (Enter: * * L 10?+C4?+7C? in IPCS while browsing ACTIVE storage.) If * * it points to an OEM module instead, contact the OEM vendor * * to determine why the SMFRTEST macro gives rc0 for type19 * * SMF records (SMF19 SMFtype19). Note: It is NOT necessary * * for SMF19/SMF69 records to actually appear in the SMF * * datasets. OEMs may force the PROCESSING for type19 / type69* * records to be performed, but not force the COLLECTION * * of those records, so that MVS is able to discard those * * records before writing them to the SYS1.MANx dataset. * *************************************************************** At times, a SWITCH command fails to occur within a large amount of time. This problem is usually seen when type19 records are being collected. This is due to the fact that SMF issues the LSPACE macro for every online device when information for SMFtype19 records is being gathered. LSPACE then causes an ENQ to be issued against each device. If an ENQ cannot be satisfied, LSPACE processing will wait. Depending on what the device is active for, the ENQ may take quite a while and the SWITCH (I) command cannot complete. Additional Keyword(s): No response from SMF swItch command. Suggestion(s) for Level1: If the problem persists with type19 recording deactivated, ask the customer to get a dump of the SMF ddress space while the switch command is hung. The RB's under the current TCB should show what module is in control at the time. If SMFDUMP issued the switch, dump its address space and ASID1, also. To see if there is any contention, issue the command D GRS,C. This problem can also occur at IPL time when module IEEMB823 invokes the LSPACE SVC (SVC78 x'SVC4E'). If at IPL, the result may be that the IPL waits until the device is available. In one customer's case, defrag jobs were being run on one system while a second system was being IPL'd. Since the defrag jobs were being run against shared DASD, the second system hung while SMF waited for the LSPACE against the shared DASD to complete. Suggestion(s) for users: Deactivate type19 / type69 recording and see if the problem persists. . If SMF is in a hang or hung situation: (added 11/14/00 LMM) - Issue the command, FORCE SMF,ARM This should trigger a dump for the SMF address space. - Use the IPCS SMFDATA command to retrieve SMF records contained in SMF's buffers. (Note, first allocate a dataset to contain these records. If necessary, refer to the SMF manual, Systems Management Facilities GC28-1783 on creating SMF datasets.) - To restart SMF, issue the SET command. For example, T SMF=BT - If there is a concern about the integrity of the SMF datasets, run the access method services VERIFY command against the dataset(s). - If one or more SMF datasets had the 'close pending' status as shown in the display command: D SMF use a different SMFPRMxx parmblib member in the SET command that does not include these datasets. (Create new SMF datasets if necessary.) Once the switch has been made, use the IFASMFDP program to dump the SMF datasets. --------------------------------------------------------------- SMFINFO This APAR is part of an effort by SMF Level2 to assist the customers and Level1 in doing PSI for apparent SMF problems. Note to Level1: Please add your name (or the customer's name) to the IP list of this APAR in the following format if you found this APAR to be helpful: . CUST#/PROB#/NAME CUST(Y/N) BO# AR## COUNTRY# 9999999/99999/Your Name N B 999 AR# 99 C 000 It isn't necessary to enter the correct Customer Number, Problem Number, Branch Office, or Area Number. You can enter nines in these fields. -----------------------------------------THANK YOU------------- Additional Keywords: 5752SC100 5752SC102
Local fix
Problem summary
Problem conclusion
Temporary fix
Comments
LEVEL1: PLEASE ENSURE THAT YOU HAVE UPDATED THE INTERESTED PARTIES LIST AS INDICATED.
APAR Information
APAR number
II02887
Reported component name
V2 LIB INFO ITE
Reported component ID
INFOV2LIB
Reported release
001
Status
CLOSED CAN
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
1987-04-27
Closed date
1987-04-28
Last modified date
2008-04-09
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":"SG19M","label":"APARs - z\/OS environment"},"Platform":[{"code":"PF054","label":"z\/OS"}],"Version":"001"}]
Document Information
Modified date:
13 December 2020