Rui Miguel Feio » MVS

VSAM Open Error Codes

Rui Miguel Feio — Sat, 24 Dec 2011 15:42:02 +0000

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

Rui Miguel Feio — Sun, 11 Dec 2011 15:12:20 +0000

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

Rui Miguel Feio — Sat, 03 Dec 2011 18:53:36 +0000

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:

0C1	OPERATION
0C4	PROTECTION / ADDRESSING
0C5	ADDRESSING

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.

XCF Group

Rui Miguel Feio — Sun, 22 May 2011 15:11:45 +0000

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

Rui Miguel Feio — Sun, 22 May 2011 15:10:09 +0000

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

XCF Application

Rui Miguel Feio — Sat, 07 May 2011 17:20:31 +0000

An application in a XCF context is a program that has various functions distributed across z/OS systems in a multisystem environment. An application or subsystem might consist of multiple instances, each running on a different system in the same sysplex. Typically, each instance performs certain functions for the application as a whole. Alternatively, each instance could perform all the application’s functions on a given system.

XCF services are available to authorized applications, such as subsystems and z/OS components, to use sysplex services.

Notes:

XCF – Cross-system Coupling Facility

Couple Data Sets

Rui Miguel Feio — Fri, 29 Apr 2011 10:59:13 +0000

XCF – a sysplex couple data set to store information about its systems, the XCF groups and members running in the sysplex, and general status information.

CFRM – The Coupling Facility Resource Management (CFRM) couple data set holds the CFRM policy, which allows you to define how MVS is to manage your coupling facility resources.

SFM – The Sysplex Failure Management (SFM) couple data set holds the SFM policy, which allows you to define how system failures, signalling connectivity failures, and PR/SM reconfiguration actions are to be managed.

WLM – The Workload Management (WLM) couple data set holds the WLM policy, which allows you to define service goals for workloads.

ARM – The Automatic Restart Management (ARM) couple data set holds the policy that defines how MVS is to manage restarts for specific batch jobs and started tasks that are registered as elements of automatic restart management.

LOGR - The system logger (LOGR) couple data set holds the policy that allows you to define log stream or structure definitions.

Cross-System Coupling Facility (XCF) Services

Rui Miguel Feio — Mon, 25 Apr 2011 14:34:57 +0000

XCF provides the services that allow multisystem application functions (programs) on one z/OS system to communicate with functions on the same or other z/OS systems. The communication services are provided through authorized assembler macros and are as follows:

Group services
Signalling services
Status monitoring services

Group Services

XCF Group Services provide ways for defining members to XCF, establishing them as part of a group, and allowing them to find out about the other members in the group. A member introduces itself to XCF through the IXCJOIN macro. If a member identifies a group exit routine, XCF uses this routine to notify this member about status changes that occur to other members of the group, or systems in the sysplex; thus, members can have the most current information about the other members in their group without having to query each other.

Signalling services

The Signalling Services control the exchange of messages between members of an XCF group. The sender of a message requests services from XCF signalling services. XCF uses buffer pools to communicate between members in the same system, and it uses buffer pools plus signalling paths (CTCs or a CF list structure) to send messages between systems in the sysplex.

Status monitoring services

Status monitoring services provide a way for members to determine their own operational status and to notify the other members of the group when that operational status changes. An installation-written status exit routine identified to XCF determines whether a member is operating normally. An installation-written group exit routine identified to XCF allows a member to maintain current information about other members in the group, and systems in the sysplex.

Server Time Protocol (STP)

Rui Miguel Feio — Fri, 18 Mar 2011 18:56:37 +0000

Server Time Protocol (STP) is a server-wide facility that provides capability for multiple z/OS systems to maintain TOD synchronization with each other and form a Coordinated Timing Network (CTN), that is, a collection of z/OS systems that are time synchronized to a time value.

The External Time Reference (ETR) connections will be replaced over time by the implementation of Server Time Protocol (STP), which makes use of coupling links to pass timing messages to the servers. Transition to STP makes it possible to have a Mixed Coordinated Network configuration. The Sysplex Timer provides the timekeeping information in a Mixed CTN. Once an STP-only configuration is established, the ETR connections are no longer needed. STP allows coexistence with Sysplex Timer in mixed configurations. The Sysplex Timer console is replaced by an HMC screen for each possible time zone.

Base Sysplex

Rui Miguel Feio — Sun, 13 Mar 2011 10:11:34 +0000

A Base Sysplex configuration is a sysplex with no Coupling Facilities. The Base Sysplex can be composed of one or more z/OS systems that have an XCF sysplex name and in which the authorized programs (members) use XCF services. XCF services are available in both single and multisystem environments. A multisystem environment is defined as two or more z/OS systems residing on one or more CPCs’ logical partitions connected through CTCs.

A Base Sysplex is the first step to implementing a Parallel Sysplex. A Parallel Sysplex is a Base Sysplex plus the use of the Coupling Facility. So, when you introduce the coupling facility, XCF exploits the coupling facility, using it as a link between z/OS systems.

The communication link between XCFs could be through channel-to-channel adapters (CTCs) that allow data movement between XCF buffers in the systems through an I/O operation. Another option for linking is a CF list structure.

Notes:

CF – Coupling Facility

CPC – Central Processor Complex

CTC – Channel-To-Channel

XCF – Cross-system Coupling Facility