Boxed Devices
Hello All... I am new to the group. Trying to activate a new IODF with a force because the new IODF contains deletes, and I receive: REASON=016B,CAN NOT DELETE DEVICE(S) 0D00-0D3F DESCTEXT=SYSTEM ERROR COMPID=SC1C3 >From a D U,,,0D00,2 command, I get: 0D00 3390 F-BOX 0D01 3390 F-BOX These devices are no longer physically located at our site. They were removed many months ago. How can I correct these devices to allow activation of the new IODF? I have configured the 2 CHPs for these devices offline from a console as well as the HMC. Still no good. I do have an open PMR with IBM, but I am also looking for other input. Thanks in advance for all help. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Boxed Devices
Kevin, I searched IBMLINK for "activate 016b" and found 2 possiblilities: II08927 - MSGIOS500I IOS5000I RC 16B 016B OA11862 - H/W ACTIVATE FAILS DUE TO WRONG SUBCHANNEL SET ID The only PTF for OA11862 is: UA19349 ( for z/OS R7 only ). The example of the message in the APAR was: MSGIOS1500I REASON=016B,CAN NOT DELETE DEVICE(S) d FROM CSS c DESCTEXT=SYSTEM ERROR - DIAGNOSTIC INFO 4015 010A 01 The message you received didn't have the "FROM CSS c" information nor did it have the "DIAGNOSTIC INFO 4015 010A 01" If your z/OS is R7, then maybe the APAR might apply. If not, maybe the INFO APAR: II08927 might apply. HTH Glenn Miller -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Boxed Devices Ate My Job
Our IMS system periodically submits batch jobs to offload its logs. Of course the job never fails until we run for 9 days unattended over the Christmas break. Some unexplained event caused the twin fiber links to our VTS to drop offline for about 10 minutes, generating sticky messages IOS581E and IOS208I. The rub then comes that the system generates messages IOS102I and IOS451I and boxes the device when the paths come online. Then some time later IMS submits his batch job which fails with a JCL error due to allocation failure because all 64 virtual tape drives have been boxed. No amount of COND=... will help for a JCL error so the email and text message alerts were never sent. Suggestions for automation or notification? (MPFLST only) Automatically vary the boxed device back online? Ben Alford Enterprise Systems Programming University of Tennessee -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Boxed Devices Ate My Job
If you have some sort of automation package like Mainview for IMS or AutoOperator, you could have it change your archive job to use DASD rather than tape when it sees your VTS's go boxed. Then your IMS's don't go belly up because they ran out of OLDS, and your archives don't get backed up either. Norris Jackson The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you received this message in error, please contact the sender and delete the material from all computers. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Ben Alford Sent: Wednesday, December 31, 2008 1:11 PM To: IBM-MAIN@bama.ua.edu Subject: Boxed Devices Ate My Job Our IMS system periodically submits batch jobs to offload its logs. Of course the job never fails until we run for 9 days unattended over the Christmas break. Some unexplained event caused the twin fiber links to our VTS to drop offline for about 10 minutes, generating sticky messages IOS581E and IOS208I. The rub then comes that the system generates messages IOS102I and IOS451I and boxes the device when the paths come online. Then some time later IMS submits his batch job which fails with a JCL error due to allocation failure because all 64 virtual tape drives have been boxed. No amount of COND=... will help for a JCL error so the email and text message alerts were never sent. Suggestions for automation or notification? (MPFLST only) Automatically vary the boxed device back online? Ben Alford Enterprise Systems Programming University of Tennessee -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Boxed Devices Ate My Job
Hi Ben, We don't have IMS, but we do have other tasks that submit jobs, so pehaps this method will be helpful - it works well for us. We have the submitted JCL IEFBR14 allocate and catalog a dataset instead of running the 'real' job. We tell our scheduling system (ZEKE) to submit a job (in this case the one that would do the log cleanup) when it 'sees' that dataset catalogued. One of ZEKE's features is that it checks to see if the devices needed to run the job are available. If not, then ZEKE can trigger a notification of whoever would need to take care of the problem. For us, ZEKE notifies a DBA by text message to a cell phone if a specific database job can't run while we are unattended. If you don't have ZEKE, it's likely that you could do the same sort of thing with your scheduling system. We don't have any automated ops either. Linda Mooney -- Original message -- From: Ben Alford > Our IMS system periodically submits batch jobs to offload its logs. Of > course the job never fails until we run for 9 days unattended over the > Christmas break. Some unexplained event caused the twin fiber links to > our VTS to drop offline for about 10 minutes, generating sticky messages > IOS581E and IOS208I. The rub then comes that the system generates > messages IOS102I and IOS451I and boxes the device when the paths come > online. Then some time later IMS submits his batch job which fails with > a JCL error due to allocation failure because all 64 virtual tape drives > have been boxed. No amount of COND=... will help for a JCL error so the > email and text message alerts were never sent. > > Suggestions for automation or notification? (MPFLST only) Automatically > vary the boxed device back online? > > Ben Alford Enterprise Systems Programming > University of Tennessee > > -- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO > Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
