IBM Mainframe Forum

Hi everyone!
I am currently trying to execute a payment simulation using JCL, here there's the code:



I then run SUBMIT, jcl submits the job, but when I check in SDSF in the output queue then I got this message:
IEF4501 USERID someuser someuser - ABEND=S622 U0000 REASON=000335 TIME=13.58.25

I have already checked the message IEF4501 on the manual and it says "A job step abnormally ended." but I can't see any errors in my code.
Would you please help to spot the error[s]???
Thank you!

The JCL is badly edited (that could never run) and should have been enclosed in Code tags, but pass that. The S622 abend refers to the TSO session from which the job was submitted, not the job itself. Look up the possible reason for a S622 abend in the z/OS MVS System Codes manual, and decide which might apply.

Hello,

As Akatsukami mentioned, the posted "jcl" will not execute.

Suggest you copy/paste the actual job submitted so we can see what you really have. Also post all of the diagnostic information presented.

Use the Code tag for these.

Have you referenced the fine manual to see what a 622 abend is ?

Thank you everyone for replying!
I have checked the manual and this is what I found:
622
Explanation: A task entered from a Time Sharing Option (TSO) terminal ended for one of the following reasons:
The system encountered one of the following errors while constructing control blocks for TSO:
The system encountered a multiple-step procedure.
The prompting task ended abnormally.
The terminal user signaled ATTN during LOGON scheduling.
The user submitting the job disconnected his or her terminal from the system.
The terminal malfunctioned.

I think my error is " The system encountered a multiple-step procedure." but I don't really know how to fix it, can anyone help me with this? The code is all that I previously posted

There's only "PAYMENT JOB MSGCLAS=H" at the beginning of the file

clapclash, do you realize that JCL requires each and every statement begin with // ? You have made multiple posts of your purported JCL, and not one of those lines start with //. This lack of the proper starting characters, alone, could explain your problem.

Furthermore, your post has 'EXCE' instead of 'EXEC' but I doubt you're getting far enough for the JES converter/interpreter to have a problem with the keyword.

Rober I know that each statement starts with // and I'm sorry for not posting it together with the code. I have already changed EXCE to EXEC, the funny thing now is that when I check in SDSF the output queue after submitting this job I cannot see any output job, not even wrong, I've already checked the LOG but there's nothing there as well. Do you have any idea?

Usually when a job is submitted but does appear on the spool, it is because the JOB statement is incorrectly coded and JES flushed the job since it did not recognize the JOB statement.

Also, the problem with what you are doing is that you are editing what you post. This is bad because sometimes the details you omit are FAR more important than what you include. We like to see mainframe output, cut from the screen and pasted into your post.

2 points to add here
1. you are specifying MSGCLAS instead of MSGCLASS (job not run JCL error)
2. you pasted the code PAYMENT EXCE PGM=PAYMENT, REGION=1024K Even if you changed EXCE to EXEC, this will also cause a job not run JCL error, 'expected continuation not received' due to the space after the comma.
These are the reasons responders NEED to see the actual JCL, we know a lot (generally) but are not mind readers