QSH CMD(&QSHCM)
RTVJOBA JOB(&JOBNAME) USER(&JOBUSER) NBR(&JOBNUM)
RCVMSG MSGTYPE(*COMP) RMV(*NO) MSGDTA(&MSGDTA) MSGID(&MSGID)
CRTPF FILE(QTEMP/SFTPLOG) RCDLEN(136)
MONMSG MSGID(CPF0000)
CPYSPLF FILE(QPRINT) TOFILE(QTEMP/SFTPLOG) +
JOB(&JOBNUM/&JOBUSER/&JOBNAME) +
SPLNBR(*LAST) MBROPT(*REPLACE) +
CTLCHAR(*PRTCTL)
IF (&MSGID *EQ 'QSH0005') THEN(DO)
CHGVAR &RC %BIN(&MSGDTA)
CALL PGM(SFTPLOG) PARM(&OK)
ENDDO
DMPCLPGM /* DUMP WILL SHOW RC AS 0 (SUCCESS) OR 1 (FAIL) */
ENDPGM
**************************************************************************
H/TITLE SFTPLOG - Check SFTP log for success/failure
H DATEDIT(*YMD)
H* Program Name : SFTPLOG - Check SFTP log for success/failure
**************************************************************************
Fsftplog ipe f 136 disk
**************************************************************************
dsearchfor s 10
dpos s 4s 0
**************************************************************************
* Input Parameters
isftplog AA 01
* Record type
i 1 136 irec
**************************************************************************
C *ENTRY PLIST
C PARM OK 1
c eval searchfor = 'Uploading'
c exsr search
c if pos <> 0
c eval ok = 'Y'
c endif
c eval searchfor = 'Fetching '
c exsr search
c if pos <> 0
c eval ok = 'Y'
c endif
**************************************************************************
C search begsr
**************************************************************************
/free
pos = %scan(searchfor: irec :1);
/end-free
c endsr
Paul
-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Jerry Draper
Sent: Monday, July 09, 2018 6:07 PM
To: Midrange Systems Technical Discussion
Subject: monitoring batch shell scripts
Let's say you have a CL pgm that does a CALL QP2BATCH(xx.sh <parms>)
where control goes over to the *ix side of the world.
Let's say that the xx.sh script runs and sFTP, python, or perl script.
What happens if one of these err out. How would the CL calling process
know?
We had one case where an sFTP script was erring out because the server
was displaying a connection msg. Once we piped std err to a file all
completed normally.
Thanks,
Jerry
midrange.com
