IBM Mainframe Forum

Hello there,
I was hoping if someone can shed some light on the following issue.
I have JCL which creates a dataset and then the next step in jcl calls a rexx script.

In the form
,//SYSTSIN DD *
,EXEC 'MYID.KA.REXX.EXEC(TEMP1)' 'MYID.KA.DISPDB.OUTPUT'

This rexx does some logic on the file generated in first step and depending upon the outcome, it prepares another JCL to send email.
My issue is whenever that REXX script runs the command ADDRESS TSO "SUBMIT " JCLDSN
The job fails with
READY
EXEC 'MYID.KA.REXX.EXEC(TEMP1)' 'AR62199.KA.DISPDB.OUTPUT'
IKJ56283I ACCOUNT INVALID IN JOB CARD. JOB CANCELLED
READY
END

The issue is the job card is not invalid.
If I run the rexx script directly via option 6 , it works fine and sends the email.
The email JCL generated by the REXX (JCLDSN) if submitted directly works fine
But for some reason when I enter the submit command in rexx it fails

Any idea?
Thanks in advance.

I don't know if you tried searching for the message. I did and got the result in this manual. The explanation was not real helpful: the message text comes from a user exit; your installation code, in other words. You should raise this issue there.

But as you can see from my message that this message is actually not representing the real issue.
The same user exit works if I directly run the exec. Also the job card is valid as the same jcl can be directly submitted,
The issue only appears if I submit this same job from within REXX using submit command.

whatever Your point of view, the system is right and You are wrong full stop
the message represents the real issue ( with Your setup, most probably the way Your SUBMIT exit is coded )

You are just telling that
under FOREGROUND ( ONLINE/INTERACTIVE/SCREEN TSO SESSION ) the script works
under BACKGROUND ( BATCH TSO SESSION ) the script does not work

ask the people who wrote the SUBMIT exit, not us!

Well, there is one other possibility, though it has to go back to arshadhrashid to investigate. This possibility is the Rexx exec executes differently in batch than in online TSO. We are assuming the Rexx exec doesn't do anything except submit the data set. I'm thinking it constructs a job that includes the data set, and then submits the job with a faulty job card.

Of course, the most likely outcomes are that arshadhrashid will just come back and tell us, "You don't get it; I'm arshadhrashid and I never do anything wrong!" or he doesn't come back to us at all.

Thank you all for trying to help me.
We have not modified any IBM supplied EXISTS in our shop so is the SUBMIT exit.

I think I am not able to explain my issue clearly.

yes the rexx scripts creates a JCL in a dataset and then that datset is submitted via the same REXX, this is where I get Invalid job card error.
But if the same JCL which was created by this REXX, submitted directly via TSO command it works fine and no invalid job card error is issued.
In fact the job card is completely valid.

And Mr. Steve, If I ever had thought that I never make a mistake I would not initiate this thread to begin with.

thanks

the message is clear!
IKJ56283I ACCOUNT INVALID IN JOB CARD. JOB CANCELLED
the IKJEFF10 exit checks the account number in the job card and is telling You that it is invalid

did You try to understand it ???

IKJ56283I exit_message
Explanation: The inserted message text is supplied by the SUBMIT installation exit (IKJEFF10). The exit will use a return code to tell SUBMIT whether to terminate or continue execution after the message has been issued.
Detected by: IKJEFF09

again stop complaining with US and start working with Your support...
also as advised before find out the differences between the batch and interactive processing
since the results are different somewhere along the chain something is different!

in fact the job card is completely valid.

what a truckload of whale excrements ...
if it were valid we would not be her wasting time
in such situation what You think/feel is completely irrelevant
some process in Your system determined that the account info in the job card is invalid
solution...
1) fix the job card to satisfy the <process>
2) fix the <process> to accept Your job card
no other alternatives here

but maybe the TS is a high ranked manager in his organization ...
the symptoms are ...
he is in deep sh**
he does not know how to get out of it
blames us for it

Gentlemen ,

I never complained to you about anything nor I am putting the blame upon you.
I was just seeking advise of fellow professionals.

Please respect the rules of this forum and mind your language.
If you can't help please don't even respond.

Obviously, your REXX submit is not submitting the same job card as option 6 -- otherwise, the system would accept the job card and you would not be getting any messages back. You do not seem to want to accept this situation. As long as your attitude is that the job card is valid (despite the FACT that your system does not agree with this assessment), it is a waste of our time to attempt to help you. You said

But as you can see from my message that this message is actually not representing the real issue.

THE REAL ISSUE IS THAT YOUR SYSTEM IS TELLING YOU THE JOB CARD IS NOT VALID BUT YOU ARE NOT ACCEPTING THIS!