VSAM Open Error Codes
Posted by Rui Miguel Feio in MVS, Storage, Tech - Mainframe on December 24, 2011
| 136(88) | Not enough Virtual-Storage Space is available for Work Areas, Control Blocks, or Buffers. |
| 144(90) | An uncorrectable I/O error occurred while VSAM was Reading or Writing a catalog record. |
| 148(94) | No record for the data set to be opened was found in the available catalog(s) or an unidentified error occurred while VSAM was searching the catalog. |
| 152(98) | Security Verification failed; the password specified in the Access-Method Control Block for a specified level of access does not match the password in the catalog for that level of access. |
| 164(A4) | An uncorrectable I/O error occurred while VSAM was Reading the Volume Label. |
| 168(A8) | The data set is not available for the type of processing you specify, or an attempt was made to open a Reusable data set with the Reset option while another user had the data set. |
| 176(B0) | An error occurred while VSAM was attempting to fix a page of Virtual storage in Real storage. |
| 180(B4) | A VSAM catalog specified in JCL either does not exist or is not open, and no record for the data set to be opened was found in any other catalog. |
| 184(B8) | An uncorrectable I/O error occurred while VSAM was completing an I/O request. |
| 188(BC) | The data set indicated by the Access-Method Control Block is not of the type that may be specified by an Access-Method Control Block. |
| 192(C0) | An unusable data set was opened for output. |
| 232(E8) | Reset was specified for a nonreusable data set and the data set is not empty. |
| 236(EC) | A permanent Staging error occurred in MSS (Acquire). |
| 244(F4) | The Volume containing the Catalog Recovery area was not mounted and verified for output processing. |
VSAM Logical Error Codes
Posted by Rui Miguel Feio in MVS, Storage, Tech - Mainframe on December 11, 2011
| 004(04) | Read past end of file |
| 008(08) | You attempted to store a record with a Duplicate Key, or there is a duplicate record for an alternate index with the unique key option. |
| 012(0C) | You attempted to store a record out of Ascending Key Sequence in Skip-Sequential Mode; record had a Duplicate Key; for Skip-Sequential processing your GET, PUT, and POINT Requests are not referencing records in Ascending Sequence; or, for Skip-Sequential Retrieval, the key requested is lower than the previous key requested. For Shared Resources, buffer pool is full. |
| 016(10) | Record not found. |
| 020(14) | Record already held in exclusive control by another requester. |
| 024(18) | Record resides on a volume that cannot be mounted. |
| 028(1C) | Data set cannot be extended because VSAM can’t allocate additional Direct-Access Storage Space. Either there is not enough space left to make the secondary allocation or you attempted to increase the size of a data set while processing SHROPT=4 and DISP=SHR. |
| 036(24) | KeyRangeswere specified for the data set when it was defined but no range was specified that includes the record to be inserted. |
| 040(28) | Insufficient Virtual Storage to complete the request. 044(2A) Work area too small. 064(40) All available strings are in use. |
| 068(44) | You attempted to use a type of processing (Output or Control-Interval Processing) that was not specified when the data set was opened. |
| 074(4A) | Trying to use keys on ESDS or RRDS. |
| 076(4C) | You issued an Addressed or Control-Interval PUT to add to a Key-Sequenced data set, or issued a Control-Interval put to a Relative Record data set. |
| 080(50) | Trying to delete from ESDS. |
| 084(54) | Using OPTCODE=LOC for a PUT. |
| 088(58) | You issued a Sequential GET request without having caused VSAM to be positioned for it, or you changed from Addressed Access to Keyed Access without causing VSAM to be positioned for Keyed- Sequential Retrieval; there was no Sequential PUT insert for a Relative Record data set, or you attempted an illegal switch between forward and backward processing. |
| 92(5C) | A PUT for update or an ERASE was issued without a previous GET for update, or a PUTIX was issued without a previous GETIX. |
| 96(60) | Changing the Prime Key or Key of Reference when making an update. 100(64 Trying to change record length. |
| 104(68) | The RPL options are either invalid or conflicting. 108(6C) RECLEN specified was larger than the maximum allowed, equal to 0, or smaller than the sum of the length and the displacement of the key field; RECLEN was not equal to record (SLOT) size specified for a Relative Record data set. |
| 112(70) | Invalid key length. |
| 116(74) | Trying to update an empty dataset. |
| 120(78) | Request was submitted by the wrong task. 132(84) An attempt was made in Locate Mode to retrieve a Spanned Record. |
| 136(88) | You attempted an Addressed GET of a Spanned record in a Key- Sequenced data set. |
| 140(8C) | Inconsistent Spanned record. |
| 144(90) | Invalid pointer (no associated base record) in an Alternate Index. |
| 148(94) | Maximum number of Alternate Index pointers exceeded. |
| 152(98) | Not enough buffers available. |
| 156(9C) | Invalid control interval. |
| 192(C0) | Invalid Relative Record number in a RRDS dataset. |
| 196(C4) | Addressed access to a Relative Record (RRDS) dataset is not allowed. |
| 200(C8) | Addressed Access or Generic Backward processing by Key thru a path is not allowed. |
| 204(CC) | Attempting a PUT in backward mode. |
| 252(FC) | Record mode processing is not allowed for a Linear data set. |
Most Common JCL Error Codes
Posted by Rui Miguel Feio in JCL, MVS, Tech - Mainframe on December 3, 2011
| S001 | An I/O error ocurred. Check reason code for exact cause. Examples are trying to read beyond End of File, trying to write to an input file or a file length error. | ||||||
| S002 | Invalid I/O record, eg attempting to write a record that is longer than the maximum record length. | ||||||
| S004 | Error occured during OPEN. Eg Invalid DCB. | ||||||
| S013 | Error OPENing a dataset, eg PDS member does not exist, record length in program doesn’t match dataset’s record length. | ||||||
| S0C1 | Operation Exception. Check for subscript errors, missing DD card, file not opened. | ||||||
| S0C4 | Protection Exception/Storage Violation. Trying to access storage not available to the program. Can be caused by a subscripting error or reading/writing a file that isn’t open. | ||||||
| S0C7 | Program Check Exception – Data. Check for spaces in a packed decimal or numeric field. Check to see if record layouts or file layouts have been changed. | ||||||
| Sx22 | Job has been cancelled. The value of x will vary depending on the way the job was cancelled. S222 means job was cancelled by a user or operator without a dump. If a TSO session times out you will probably get an S522 abend code. | ||||||
| S806 | Unable Link or Load. The job was unable to find the specified load module. Check that the job is looking at the correct Load Libraries, specify a STEPLIB if required. | ||||||
| S80A | Not enough Virtual Sorage to satisfy a GETMAIN or FREEMAIN request. | ||||||
| S822 | Unable to obtain to obtain enough space to satisfy a REGION= request May need to change REGION statement in the JCL.. | ||||||
| S878 | Not enough storage available to satisfy a GETMAIN or FREEMAIN request.. Job was anable to allocate an area of memory of the correct size. Try Specifying or amending the ‘REGION=’ JCL statement. | ||||||
| S913 | You are trying to access a dataset which you are not authorized to use. | ||||||
| Sx37 | Unable to allocate enough storage for a dataset. You might need to increase the amount of primary and secondary space to be allocated for a dataset in the ‘SPACE=’ parameter, or you may have to move the dataset to a different DASD devive which has enought space to store the dataset. ‘x’ will vary, likely Abends are SB37, SD37 or SE37. | ||||||
| U1020 | I/O Logic error. Typical reasons are; trying to write to a file opened as input; Rewrite without a previous read. See the message IGZ020I for details of the exact reason. | ||||||
| U1035 | Inavlid OPEN/CLOSE. Check there is a DD statement for the file. See the message IGZ035I for more detailed information. | ||||||
| 001 | I/O ERROR | ||||||
| 002 | I/O INVALID RECORD | ||||||
| 004 | OPEN ERROR | ||||||
| 008 | I/O SYNAD ERROR | ||||||
| 013 | OPEN ERROR | ||||||
| 028 | PAGING I/O ERROR | ||||||
| 0CX | PROGRAM CHECK EXCEPTIONS:
|
||||||
| 706 | NON-EXECUTABLE PROGRAM | ||||||
| 804 | INSUFFICIENT VIRTUAL STORAGE | ||||||
| 806 | UNABLE TO LOAD (LINK ETC) PROGRAM | ||||||
| 80A | INSUFFICIENT VIRTUAL STORAGE | ||||||
| 878 | INSUFFICIENT VIRTUAL STORAGE | ||||||
| 737 | I/O ERROR | ||||||
| A14 | I/O ERROR | ||||||
| B37 | The system allocated all the primary and secondary space it could, but it still could not write the output. | ||||||
| D37 | Primary disk space was exceeded and no secondary space has been specified, or it has been exhausted. | ||||||
| E37 | This often occurs when you try to add members to a PDS, and you get E37 ABEND. It occurs because the PDS Directory require more space for its members, than it was initially alloted. |
IBM zEnterprise Announcement
Posted by Rui Miguel Feio in Tech - Mainframe, zSeries on July 24, 2011
This animation features the key announcements for the 2011 IBM zEnterprise launch including: the zEnterprise 114, Linux support for select IBM System x blades, and Unified Resource Manager APIs and key enhancements to the z196.
IBM zEnterprise Cloud & Consolidation
Posted by Rui Miguel Feio in Tech - Mainframe, zSeries on July 24, 2011
Highlights of the benefits of using the IBM zEnterprise System for cloud computing and consolidation. It describes how organizations can speed up the delivery of new innovations while lowering infrastructure costs.
What is IBM zEnterprise System?
Posted by Rui Miguel Feio in Tech - Mainframe, zSeries on July 24, 2011
What is RACF and what does it do?
Posted by Rui Miguel Feio in RACF, Tech - Mainframe on July 1, 2011
RACF (Resource Access Control Facility) helps to secure an organization’s Mainframe environment by providing:
- Flexible control of access to protected resources
- Protection of installation-defined resources
- Ability to store information for other products
- Choice of centralized or decentralized control of profiles
- An ISPF panel interface
- Transparency to end users
- Exits for installation-written routines.
A typical RACF protected system is organized in a certain manner. Users that need access to the same resources are gathered together and placed into groups. These groups are then given access to the data and resources needed by its members:
1. Several Users
2. Are placed into Groups
3. Which are given access to Resources.
Types of JCL Statements
Posted by Rui Miguel Feio in JCL, Tech - Mainframe on June 30, 2011
JOB – Identifies the beginning of a job. The JOB statement informs the operating system of the start of a job, gives the necessary accounting information, and supplies run parameters. Each job must begin with a single JOB statement
EXEC – Indicates what work is to be done. EXEC (execute) statement is used to identify the application program, cataloged procedures or in-stream procedure that the job is to execute and to tell the system how to process the job.
DD – (Data Definition) Identifies what resources are needed and where to find them. A DD statement must be included after the EXEC statement for each data set used in the step. The system ensures that the requested I/O devices can be allocated to the job before execution is allowed to begin.
XCF Group
Posted by Rui Miguel Feio in Glossary, MVS, Tech - Mainframe on May 22, 2011
A group is the set of related members defined to XCF by a multisystem application in which members of the group can communicate with other members of the same group. A group can span one or more of the systems in a sysplex and represents a complete logical entity to XCF.
Notes:
XCF – Cross-system Coupling Facility
XCF Member
Posted by Rui Miguel Feio in Glossary, MVS, Tech - Mainframe on May 22, 2011
A member is a specific function (one or more routines) of a multisystem application that is joined to XCF and assigned to a group by the multisystem application. A member concept applies to all authorized routines running in the address space that issued the IXCJOIN macro service. Only for termination purposes (resource clean-up), the member can be associated with an address space, job step, or task.
XCF terminates the member when its association ends. The same address space can have more than one group.
Notes:
XCF – Cross-system Coupling Facility
Follow Me!