|
View previous topic :: View next topic
|
| Author |
Message |
Rajesh_98
New User
Joined: 20 Nov 2019
Posts: 1
Location: India
|
|
|
|
Hi,
I'm running one rexx script with the JCL which contains SYSDSN() keyword.
what issue I'm facing is.
1. If I run the same rexx directly by EX in front of the script containing file. its working as expected. SYSDSN returning OK for existing file and 'DATASET NOT FOUND' for non-existing files.
2. But when I run the same rexx through JCL, SYSDSN returns 'DATASET NOT FOUND' for both (existing and non-existing).
So is there any constraint that we can't run SYSDSN though JOB?
or some additional parameter required to be provided in JCL to get this working? |
|
| Back to top |
|
 |
prino
Senior Member
Joined: 07 Feb 2009
Posts: 1306
Location: Vilnius, Lithuania
|
|
|
|
| We might be able to tell, if you had actually bothered to post the JCL... |
|
| Back to top |
|
|
steve-myers
Active Member
Joined: 30 Nov 2013
Posts: 917
Location: The Universe
|
|
|
|
| prino wrote: |
| We might be able to tell, if you had actually bothered to post the JCL... |
AND the Rexec EXEC |
|
| Back to top |
|
|
Willy Jensen
Active Member
Joined: 01 Sep 2015
Posts: 712
Location: Denmark
|
|
|
|
| One thought that springs to mind is the PREFIX setting. This is typically set by the TSO login script, but not when using REXX in batch. Try to put the datasetname in quotes in both cases. Also list the profile PREFIX value in both cases. |
|
| Back to top |
|
|
|
|
