Description: This ABEND is caused by a hardware detected virtual
address translation error, or a storage protection
violation. The cause of the error is indicated by the
reason code, as follows:

Reason Code Description
-----------------------------------------------------------------------
4 Protection Exception: the protect key in the currently
executing program's PSW does not match the protect key of an
instruction operand or a storage area that the program was
trying to reference.

References to pages protected with the PGSER PROTECT service
or specified shared with a read-only view to the IARVSERV
service can also cause this exception.

10 Segment translation exception: a program that was running
disabled for interrupts tried to reference storage while
the page table for that storage was paged out. To correct
the error, page-fix the storage before a program running
disabled attempts to reference it.

Another possible cause is that a program tried to
reference storage that had not been obtained. To correct
the error, allocate the storage before attempting to
reference it.

Finally, a program running in a subspace attempted to
reference storage that was not accessible to the subspace
at the time of error. To correct the error, ensure that
the program running in a subspace references only the
storage assigned to that subspace, or storage that can be
referenced by all subspaces.
11 Page-translation exception. This error is caused by
one of the following:

A program that was running disabled attempted to
reference storage while that storage was paged
out. To correct the error, page-fix the storage
before a program running disabled attempts to
reference it.

A program attempted to reference storage that had
not been obtained. To correct the error, allocate
the storage before attempting to reference it.

A program running in a subspace attempted to
reference storage that was not accessible to the
subspace at the time of error. To correct the
error, ensure that the program running in a subspace
references only the storage assigned to that subspace, or storage that can be referenced
by all subspaces.

12C SMS abend. The reason code is X'12C'.

User Action: Correct the program logic error that generated the invalid
address or storage reference. When analyzing the dump,
remember that the PSW saved when an 0C4 abend occurs may
point at the failing instruction or it may point at the
next instruction after the failing instruction.

Check to ensure that your program is obtaining, using, and
freeing storage properly. Moving data to a zero address
or to an address less than 512 (decimal) is a very
frequent cause of this abend.

COBOL: Invalid address was referenced due to subscript error
or bad parameter passed
In group move, receiving record variable length
defined incorrectly
Tried moving variable length record that was larger
than target field size
Tried to read or write a file which was not open
Used DD DUMMY with logic that moves high values to
FD
Tried to call within COBOL SORT I/O procedure
Tried to "goback" in the SORT output procedure

***** The abend occurred while processing a request for system service *****
***** The following is the status of the program that made the request *****

.
.
.
.
Last instruction was 0A14 - SVC 20 (CLOSE)
.
.
.

This step is an export step that exports only the catalogue information of the VSAM dataset to an ordinary PS file.
The DCB parameter coded for the ordinary PS out put file is

Code:

// DCB=(DP.DSCB,BUFNO=20),

I read that the Logical record length (LRECL) and the record format (RECFM) will be automatically cared by the system while exporting the VSAM dataset. Therefore, I thought it would be because of DP.DSCB. I tried a test run by removing DP.DSCB in DCB parameter. However, the job got abended again with S0c4 error. Next I tried by removing the BUFNO=20 and having DP.DSCB in the DCB parameter. Goodness the job ended fine.

When I did looked in to the output dataset it contains only the catalogue information that is only two lines of information. I doubt this might have been happened because of huge amount of buffer allocation.

Kindly explain me what would have happened because of buffer allocation and/or this might be because of any other reasons.

I am thankful to Mainframe forum that helped me in many ways and all people who helped me a lot in clarifying my queries.

Thanks
Prasannaa S

Edited: Please use BBcode when You post some code, that's rather readable...Anuj