0c1 Error
Contents |
AN I/O ERROR WHEN READING A STORAGE POOL VOLUME AIX z/os A fix is available Obtain the system completion code=0c1 reason code=00000001 fix for this APAR. Subscribe You can track all active APARs
Mainframe Abend Codes And Resolution
for this component. APAR status Closed as program error. Error description The server may abend with 0C1 (operation system abend code 0c1 exception) or with other completion codes when processing an I/O error received while reading or writing from a storage pool volume. LE may provide a CEEDUMP showing the
User Abend Codes In Mainframe
abend occurred in bdBatch. The following is an example: Traceback: DSA Entry E Offset Statement Load Mod 1 CEEKDUMP +00000DB2 CEEPLPKA 2 CEEVSSFR +00000012 CEEBINIT 3 CEEHDSP +000041B0 CEEPLPKA 4 CEEHRNUH +00000096 CEEPLPKA 5 bdBatch +00C12C94 ANRSERV 6 DsReadSeg +000007E0 1016 ANRSERV 7 DoReadSeg +00000076 10459 ANRSERV 8 AuxAsSource +00000A1A 8669 ANRSERV 9 SsAuxSrcThread +000001C2 5014 ANRSERV mainframe abend codes list pdf 10 StartThread +00000094 2817 ANRSERV 11 CEEVROND +000011F4 CEEPLPKA 12 CEEOPCMM +000009A2 CEEBINIT LE may also record the following message in the CEEDUMP: CEE3201S The system detected an operation exception (System Completion Code=0C1). From entry point bdBatch at compile unit offset +00C12C94 at entry offset +00C12C94 at address 23A129CC. The following may also be recorded in the JOBLOG: IEA995I SYMPTOM DUMP OUTPUT USER COMPLETION CODE=4039 REASON CODE=00000000 TSM Versions Affected: TSM 5.5 z/OS servers only Customer/L2 Diagnostics (If Applicable): None Initial Impact: Medium Additional Keywords: None Local fix ZAP can be obtained by contacting server support. Problem summary **************************************************************** * USERS AFFECTED: All Tivoli Storage Manager server users. * **************************************************************** * PROBLEM DESCRIPTION: See error description. * **************************************************************** * RECOMMENDATION: Apply fixing level when available. This * * problem is currently projected to be fixed * * in levels 5.5.4.2 and 5.5.5. Note that this * * is subject to change at the discretion of * * IBM. * **************************************************************** * Problem conclusion This problem was fixed. Affected platforms: z/OS
Disk space problem Below is a summary of the common messages that could occur. Each message is identified by a message number, and is formatted as: NNNNNNN ccc-rr jjj sss ddname where NNNNNNN is the error message number ccc is the system completion code
Abend=s0c1 U0000 Reason=00000001
associated with the message rr is the return code associated with the message jjj is the job
Db2 Abend Codes
name sss is the step name ddname is the file associated with the problem Message Number Parameters/Description IEA702I 80A-1 There is not enough error in db2 storage to run the request program IEA703I 806-x x=4 The requested program could not be found. Check the JCL STEPLIB or JOBLIB statements to be sure they define the library containing the requested program. x=8 An uncorrectable input-output error has occurred. http://www.ibm.com/support/docview.wss?uid=swg1PM09499 Try to run the job again. If the error reoccurs, consult your technical support staff IEC015I A34-04 An attempt was made to read an unopened file. IEC020I 001-x x=1, 3, or 4 The dataset characteristics don't match the specified file. Check your FD, JCL and data set information x=2 An error occurred when the program tried to close the file x=5 The program tried to read the file after end of file had been reached. IEC030I B37-04 There is no space http://faculty.madisoncollege.edu/schmidt/mainframe/abendcodes.html left on the disk volume The data set has reached it's limit of space The disk volume table of contents is full IEC031I D37-04 The file has used up all of its space IEC032I E37-x x=04 All available disk space is used up IEC141I 013-x x=10, 34 The block size and record length are both 0 or the block size is not a multiple of the record length. x=20 The record format indicates that the file is a blocked file, but the block size is not a multiple of the record size. x=60 The record format indicates that the file is an unblocked file, but the block size does not equal the record length x=68 The block size exceeds the maximum allowable IEC143I 213-x x=04 1) An incorrect volume or data set name parameter 2) Data set not found on disk 3) The data set has been deleted x=08 Password violation x=18, 1C I/O error Common Completion Codes - Details Code Probable Cause 001 I/O Error Attempt to read after AT END Referring to an I/O area before opening and reading a record Reading a wrong length record 002 I/O Error DD statement doesn't match FD 013 Something doesn't match up between the program and the DD statement. Check the system message IEC141I for a more complete description of the error 04x I/O Error Invalid or missing data set information. Check the file description 06x Error closing a file 09x File opening pro
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker http://www.mqseries.net/phpBB/viewtopic.php?t=3160&sid=737ab9fe57819bb46d23b5961c48c0e2 Support
MQSeries.net Forum Index » General IBM MQ Support » MQOPEN 0c1 error. (Mainframe batch program) MQOPEN 0c1 error. (Mainframe batch program) « View previous topic :: View next topic » Author Message krondorl Posted: Wed May 15, 2002 10:28 am Post subject: MQOPEN 0c1 error. (Mainframe batch program) NewbieJoined: 15 May 2002Posts: 8 Hi there, I have been struggling with a very strange problem. I wrote a mainframe cobol batch program that takes 2 parms from the JCL. One parm is to abend code connect to the correct Q Manager and the other is for which of 2 types of data to put on the queue. The compile completes without errors. Now to the problem. When I run the program, I get "CEE3201S The system detected an operation exception." on the MQOPEN command. The last couple of runs I did a test and put in a qmgr name that doesn't exist in our system and the result was that it still connects with a mainframe abend codes return code of 0. Which is a mistake in the first place. Would anyone have a clue as to why this is happening? (Just a quick note: I also compiled and ran the sample code that comes with MQ and I get the same errors.) KD. Back to top oz1ccg Posted: Thu May 16, 2002 12:42 am Post subject: YatiriJoined: 10 Feb 2002Posts: 628Location: Denmark Hi, when you're linking the program, which stub are you including ? CSQBSTUB og CSQCSTUB ? My guess is CSQCSTUB..... but CSQBSTUB is the right one... _________________Regards, Jørgen Home of BlockIP2, the last free MQ Security exit ver. 3.00 Cert. on WMQ, WBIMB, SWIFT. Back to top krondorl Posted: Thu May 16, 2002 4:56 am Post subject: Linked Stub!! NewbieJoined: 15 May 2002Posts: 8 DOH!!!! I was using the CSTUB. I must say that out of 6 people that looked at it not one of use (and 3 of them are the company MQ support people) noticed that!! I wasn't even aware there were 2 version, but now that I think about it, it only makes sense that there should be!! Thanks!! Everything works now!! Yee Ha!! Kd. Back to top Display posts from previous: All Posts1 Day7 Days2 Weeks1 Month3 Months6 Months1 Year Oldest FirstNewest First Page 1 of 1 MQSeries.net Forum Index » General IBM MQ Support » MQOPEN 0c1 error. (Mainframe batch program) Jump to: Select a forumGeneral Discussion----------------Read First for All N