Re: IEFC614I
It may be helpful if these kinds of datasets are allocated without secondary extents. -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Peter Vander Woude Sent: Wednesday, October 07, 2009 3:15 PM To: IBM-MAIN@bama.ua.edu Subject: IEFC614I We had a job failure, during submission, recently, that got the following message: IEFC614I PROCLIB DEVICE I/O ERROR SEARCHING FOR PROCEDURE/INCLUDE I know that just a few seconds before this job was submitted, a daily defrag ran, and had completed, on the volume, that one of the proclibs is on. We do exclude the proclib from being moved, but am wondering what could have caused this issue? I've got folks asking about determining what the root cause was so we can eliminate this issue in the future. Since I can't recall ever running into this, I'm not sure really how to respond, and would appreciate ANY input on this. Pete -- 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 NOTICE: This electronic mail message and any files transmitted with it are intended exclusively for the individual or entity to which it is addressed. The message, together with any attachment, may contain confidential and/or privileged information. Any unauthorized review, use, printing, saving, copying, disclosure or distribution is strictly prohibited. If you have received this message in error, please immediately advise the sender by reply email and delete all copies. -- 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: IEFC614I
snip IEFC614I PROCLIB DEVICE I/O ERROR SEARCHING FOR PROCEDURE/INCLUDE /snip The cure to the problem has been addressed by other but Hal's point is probably the cause, more so than a defrag, with the PROCLIB excluded. If the PROCLIB goes into extents while it's open you should get this error for anything in the new extent until it's closed/opened. Jack Kelly 202-502-2390 (Office) -- 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
IEFC614I
We had a job failure, during submission, recently, that got the following message: IEFC614I PROCLIB DEVICE I/O ERROR SEARCHING FOR PROCEDURE/INCLUDE I know that just a few seconds before this job was submitted, a daily defrag ran, and had completed, on the volume, that one of the proclibs is on. We do exclude the proclib from being moved, but am wondering what could have caused this issue? I've got folks asking about determining what the root cause was so we can eliminate this issue in the future. Since I can't recall ever running into this, I'm not sure really how to respond, and would appreciate ANY input on this. Pete -- 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: IEFC614I
I use to get this at least once a month. We had some programmers running COMPRESS (IEBCOPY) on their PROCLIB that was in The JES2 JCL. The solution is to use the PROCLIB statements in JES2 rather than the JCL concatenations. Then you should not see this issue. Lizette We had a job failure, during submission, recently, that got the following message: IEFC614I PROCLIB DEVICE I/O ERROR SEARCHING FOR PROCEDURE/INCLUDE I know that just a few seconds before this job was submitted, a daily defrag ran, and had completed, on the volume, that one of the proclibs is on. We do exclude the proclib from being moved, but am wondering what could have caused this issue? I've got folks asking about determining what the root cause was so we can eliminate this issue in the future. Since I can't recall ever running into this, I'm not sure really how to respond, and would appreciate ANY input on this. -- 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: IEFC614I
There are potentially 2 ways out of this depending on how you coded your proclibs. Perferred method says you are using jes2 dynamic procs, in which case a $TPROCLIB will open/close reallocate them or by chance if you have them in the JCL and have an alter PROCxx coded... you can force JES2 to close/open proc00 by Running a batch job with /*JOBPARM PROCLIB=PROCxx an alternate other assuming the error is with PROC00 Thanks Ms. Terri E. Shaffer terri.e.shaf...@jpmchase.com Engineer J.P.Morgan Chase Co. GTI DCT ECS Core Services zSoftware Group / Emerging Technologies Office: # 614-213-3467 Cell: # 412-519-2592 -Original Message- From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of Lizette Koehler Sent: Wednesday, October 07, 2009 6:20 PM To: IBM-MAIN@bama.ua.edu Subject: Re: IEFC614I I use to get this at least once a month. We had some programmers running COMPRESS (IEBCOPY) on their PROCLIB that was in The JES2 JCL. The solution is to use the PROCLIB statements in JES2 rather than the JCL concatenations. Then you should not see this issue. Lizette We had a job failure, during submission, recently, that got the following message: IEFC614I PROCLIB DEVICE I/O ERROR SEARCHING FOR PROCEDURE/INCLUDE I know that just a few seconds before this job was submitted, a daily defrag ran, and had completed, on the volume, that one of the proclibs is on. We do exclude the proclib from being moved, but am wondering what could have caused this issue? I've got folks asking about determining what the root cause was so we can eliminate this issue in the future. Since I can't recall ever running into this, I'm not sure really how to respond, and would appreciate ANY input on this. -- 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 This communication is for informational purposes only. It is not intended as an offer or solicitation for the purchase or sale of any financial instrument or as an official confirmation of any transaction. All market prices, data and other information are not warranted as to completeness or accuracy and are subject to change without notice. Any comments or statements made herein do not necessarily reflect those of JPMorgan Chase Co., its subsidiaries and affiliates. This transmission may contain information that is privileged, confidential, legally privileged, and/or exempt from disclosure under applicable law. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or use of the information contained herein (including any reliance thereon) is STRICTLY PROHIBITED. Although this transmission and any attachments are believed to be free of any virus or other defect that might affect any computer system into which it is received and opened, it is the responsibility of the recipient to ensure that it is virus free and no responsibility is accepted by JPMorgan Chase Co., its subsidiaries and affiliates, as applicable, for any loss or damage arising in any way from its use. If you received this transmission in error, please immediately contact the sender and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. Please refer to http://www.jpmorgan.com/pages/disclosures for disclosures relating to European legal entities. -- 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
