IOS command reject after ipl

Question

We were operating at a disaster recovery site. We IPLd our mainframe system to a VMax box. We began receiving IOS command rejects from devices. EMC Article 000477620 says: Issue Error Message: IOS000I-ccuu-chp-IOE-E7-0E00-00000000-volser-jobname Error Message Detail: IOS000I 2B1F,0A,IOE,E7,0E00,,00000000,volser,jobname, 000010001FFFFFF01701000000000014081213AC2B22FEF0001E00E000002008 Scratch processing showed an IOS000I message indicating a Short Long Busy condition. LOGREC shows the maximum number of retries performed by IBM ERP processing. This issue is more likely to occur during a SCF MSC cycle window. The IOS000I message ill appear in the job log and the following records will be seen in the EREP Event History report. These records will be written at the time of the IOS000I message: MMM DD HH:MM:SS.nn CCUU PERM ERROR UnitCHeck Job JJJJJJJJ on XXXX LPAR. MMM DD HH:MM:SS.nn N/A SFTSYM 01 PIDS/5695DF111 RIDS/IECVDERP#L RIDS/IECVDERP PCSS/UNITCHK PCSS/PERMERR JOBN/JJJJJJJJ MMM DD HH:MM:SS.nn N/A SFTSYM 01 PIDS/ESFHSCR PIDS/EMC#SRX PCSS/ESFTRWR0 PCSS/ERASE#COND PCSS/BACKEND MMM DD HH:MM:SS.nn CCUU PERM ERROR UnitCHeck Job JJJJJJJJ on XXXX LPAR.   Cause Thin reclaim processing should have delay retries based on the returned sense data. ------ We did have SCF started, so I feel that this is probably the reason. However, we re-IPLd without SCF, and still saw the errors. My question, then, is it possible that the first IPL could cause this issue to extend across to the second IPL? Thanks! Rod PS.. my first post of this kind, hope it hit the correct following..

PedalHarder · Answer

The cause statement in the above KB article is related to thin reclaim. This means the array is thin provisioned and reclaim processing is in use. Does this describe your environment? The IOS message alone is only half the story. There will be logs and diagnostics on the array to review and analyse to help the investigation, so you should go ahead an open a support case with EMC on this one.

MIBRod · Answer

Jason, Thanks for the reply. The DR site folks have indicated that there was an Enginuity problem in the device, so that makes my question moot. Thanks again! Rod

Symmetrix

Was this post helpful?