🚀 go-pugleaf

I don't know of an FTP command that can do it in a simple fashion. One approach is to have the job send the return code to a listener somewhere, perhaps one started by the REXX exec that performs the FTP.

-----Original Message-----
From: Pfister, Nathan J CIV (US)
Sent: Monday, February 25, 2013 3:27 PM
To: TSO-REXX@VM.MARIST.EDU
Subject: FTP to JES2 Internal Reader and get RC?

I am using REXX in a CGI manner, which is submitting a job using FCAI to the JES2 Internal Reader.  Is it possible to get the RC of the JOB that is being run in this manner?

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO TSO-REXX

Not easily. Depending on what you have availalble, you could use a
REXX or Java CGI program which uses the SDSF API to retrieve the MAXCC
of the job once it has run. There is a simpler way, if you are allowed
to install the freely licensed Dovetailed Technologies Data Set Pipes.
You could then easily write a UNIX shell script CGI program to
retrieve the job status and MAXCC. The simplest way is:

http://dovetail.com/products/dspipes.html   Again, this is freely
licensed. It doesn't need to be registered. You don't even need to
tell them your name or anything. Just download it and install. It does
not require any special privileges to run. Can be installed by anyone,
not just "root" (UID==0).

lsjes -t -so -p ${jobname}

This will result in 0 or more lines of output for the job. The last
column is the return code. So something like (not a CGI!)

#!/bin/sh
#get status of job with name on command line
lsjes -t -o '*' -so -p ${1} |\
awk '{print $1 "\t" $2 "\t" $NF;}'

Will print all users' jobs (-o '*') on the output queue (-so) which
have the first parameter's value ${1} (-p ${1}) as their job name.
Just for "fun", I pipe this into awk to only print the job number,
name, and return code. The only problem with the above is that it
outputs 0 lines if the no job exists on the output queue with the
given name. If you force the user to "log on" to the web site using
standard HTTP protocol for entering the user's id and password, then
you can leave of the "-o '*' " and you'll only get jobs submitted by
the "logged on" web user.

If you need to stay with IBM supplied interfaces, then go the SDSF API
route. Or use an (E)JES facility, if you run (E)JES.

On Mon, Feb 25, 2013 at 2:27 PM, Pfister, Nathan J CIV (US)
<nathan.j.pfister.civ@mail.mil> wrote:
> Hello List;
>
>
>
> I am using REXX in a CGI manner, which is submitting a job using FCAI to the JES2 Internal Reader.  Is it possible to get the RC of the JOB that is being run in this manner?
>
>
>
> Thanks in advance.
>
>
>
> Thanks,
>
> Nathan Pfister
>
> ----------------------------------------------------------------------
> For TSO-REXX subscribe / signoff / archive access instructions,
> send email to LISTSERV@VM.MARIST.EDU with the message: INFO TSO-REXX



--
This is a test of the Emergency Broadcast System. If this had been an
actual emergency, do you really think we'd stick around to tell you?

Maranatha! <><
John McKown

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO TSO-REXX

On Feb 25, 2013, at 13:27, Pfister, Nathan J CIV (US) wrote:
> 
> I am using REXX in a CGI manner, which is submitting a job using FCAI to the JES2 Internal Reader.  Is it possible to get the RC of the JOB that is being run in this manner?
>  
Must it be a JOB?  How about using ssh to run whatever process is
needed?  The RC is available directly.

-- gil

----------------------------------------------------------------------
For TSO-REXX subscribe / signoff / archive access instructions,
send email to LISTSERV@VM.MARIST.EDU with the message: INFO TSO-REXX