Burgess,

As a guess, you should look at your JCL run log for messages associated with the 522 error. The 522 should be very rare in a batch environment (you did not specify). It can sometimes be caused by a resource contention but, the messages should show this. You may have to check with a local systems person.

FYI:

522

Explanation: All of the tasks in a job step were in an SVC wait state for the time specified in the JWT parameter in the SMFPRMxx parmlib member.

The event control block (ECB) specified in the wait request was never posted. This could be the result of waiting on the wrong ECB or not posting the correct ECB.

Module: System Management Facilities (SMF)

System Programmer Response: Correct any errors and execute the job step again. If no errors are found and the wait is expected for that particular job step, specify TIME=NOLIMIT in the EXEC statement to bypass all job step timing.

Good luck, Dennis Diskin

"DDA.RFC-822=SAS-L@VM.MARIST.EDU/P=Internet/A= /C=us" on 12/14/99 03:40:52 PM Please respond to "DDA.RFC-822=BMEVANS@AUDITOR.STATE.OH.US/P=Internet/A= /C=us" @ X400 To: "DDA.RFC-822=SAS-L@VM.MARIST.EDU/P=Internet/A= /C=us"@X400 cc:

Subject: Error Code YZBMLOK0

We are new to SAS and using SAS 6.09 on an OS/390 V2.6 machine. I could use a hint on where to look for errors (SAS or JCL).

The user got the following message in the SAS log:

NOTE: The initialization phase used 0.06 CPU seconds and 2041K. 1 DATA TEST1; SET TYPE60.TYPE60; 2 IF PROVIDER = 9999999; 3

ERROR: Never-should-happen. Code YZBMLOK0. File TYPE60.TYPE60.DATA. ERROR: Never-should-happen. Code YZBMLOK0. File TYPE60.TYPE60.DATA. ERROR: Never-should-happen. Code YZBMLOK0. File TYPE60.TYPE60.DATA. ERROR: Never-should-happen. Code YZBMLOK0. File TYPE60.TYPE60.DATA. NOTE: The data step has been abnormally terminated. NOTE: The SAS System stopped processing this step because of errors. NOTE: SAS set option OBS=0 and will continue to check statements. This may cause NOTE: No observations in data set. WARNING: The data set WORK.TEST1 may be incomplete. When this step was stopped there were 2396 observations and 916 variables.

NOTE: The DATA statement used 65.93 CPU seconds and 3444K. 4 PROC PRINT DATA=TEST1(OBS=100);

The job also ended with a 522 job timeout error. I am trying to determine whether the Code YZBMLOK0 error caused by the 522 or if the 522 caused the Code YZBMLOK0 error.

Thank you for your help, Burgess Evans