What causes a S0C1 ABEND when using // DATE statement in VISION:Builder/Two VSE JCL?

Document ID : KB000024588
Last Modified Date : 14/02/2018
Show Technical Document Details

Description:

Using a // DATE statement in VSE JCL results in a S0C1 ABEND and an MK4CV03 error message.

Solution:

While attempting to specify a system date to his VSE application using a // DATE statement in the JCL the user experienced a S0C1 ABEND and the following messages:

** MK4CV03  TYPE 9  AN UNEXPECTED INTERRUPT HAS OCCURRED.   
                  
** MK4S701  TYPE 0  DIAGNOSTIC INFORMATION DISPLAY FOLLOWS.                   
*** INTERRUPT ADDRESS(6C000002) MODE(24) ENTRY(MARKIV) MARKIV IN CONTROL.      
*** SYSTEM 0C1  IN MARKIV MODULE(??) PSW NOT IN THIS MODULE                   
*** R13 NOT POINTING AT M4COM. 

The diagnostic information indicated the problem occurs in IBM LE code attempting to convert a Lillian date to character format.

VISION: Builder provides SYSDATE and SYSDATE4 parameters for the RP statement to specify a system date to use within the application. We recommend using one of these within the program as an alternative to the // DATE JCL statement. Please refer to the VISION: Builder Specifications Manual for RP statement syntax.

If the // DATE statement in the JCL is a requirement for some reason, please pursue the issue with IBM.