I need to produce a long series of extracts to move an appgroup to an AIX cmod instance.
A last step I want, is to run the command file containing a group of arsdoc commands for
auto extracts, and to run arsdoc command file from JCL.
I gen the command file with REXX, use OPUT to copy it to omvs, use ARSZOSHL to make it r-x to run, successfully. The last step is
ARSZOSHL nohup /ars/tmp/T2.cmd &
This does not work. I receive after READY:
ARSZOSHL nohup /ars/tmp/T2.cmd &
READY
END
CEE5210S The signal SIGHUP was received.
And the commnd file is not run. I give it no hangup, and a background task with "&". But it does not run. What is missing ? I have root authority.
A couple suggestions, run this step instead:
//STEP1 EXEC PGM=IKJEFT01,
// DYNAMNBR=200
//SYSPROC DD DSN=SYS1.SBPXEXEC,DISP=SHR
//*
//SYSTSPRT DD SYSOUT=*
//*
//SYSTSIN DD *
oshell /blah/blah/blah/what you're trying to run &1
/*
ARSZOSHL is a REXX exec --- been a long time since I've had to debug any REXX but hopefully you run it with TRACE I?
Or you can try running the command like I did in this post:
http://ODUG.net/index.php?topic=690.0 (http://odug.net/index.php?topic=690.0)
Still did not run. Received:
READY
oshell nohup T2.cmd &1
OSHELL RC = 32512
OSHELL Exit Status = 127
IKJ56246I TERMINAL NOT ALLOCATED, FILE IN USE
READY
END
=====
plus in separate JES output line
1: FSUM7351 not found
I can let the job run as staright batch from z/OS, and wait for it to run to completion. That is also acceptable, and I can alreeady do that, verifying it this morning.
> I can let the job run as straight batch from z/OS
That's always my preferred solution.
Not sure what release of z/OS this came out but you know you don't have to do anything fancy with STDOUT or STDERR anymore...
//SYSOUT DD SYSOUT=*
//STDERR DD SYSOUT=*
//STDOUT DD SYSOUT=*
...another compelling reason to run this stuff in batch.