#!/bin/bash
# This is a SFTP script
sftp -oPort=6222 -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no User@TargetSys
cd folder1
put fileName
#End of script
exit $?

Regards,
Wilson

pgm

   dcl   &MsgId       *char    7
   dcl   &MsgDta      *char  128
   dcl   &ExitSts     *int           value( 0 )

   qsh cmd('exit 79')
   rcvmsg      msgtype( *LAST ) rmv( *NO ) msgdta( &MsgDta ) +
                 msgid( &MsgId )
   if ( &MsgId *eq 'QSH0005' )  do
      chgvar   &ExitSts     %bin( &MsgDta 1 4 )
   enddo

   dmpclpgm

   return

endpgm

You should be able to paste that into a CL source member, compile it and run it. It runs the most basic QShell command to set an EXIT status of “79″. After the QSH command returns, the CL receives the last message on the program’s message queue to see if it’s QSH0005. If it is, it pulls the 4-byte binary value from the received message data.

The DMPCLPGM command then dumps the program variables to show that the first four bytes of &MsgDta contain the hex value of the EXIT status and that the &ExitSts variable contains the integer representation of those four bytes. The EXIT command that is run by QSH should have the same value.

You could use RCVMSG after your MONMSG-ENDDO. The MONMSG DO-group would catch exceptions from your STRQSH command, and RCVMSG would receive whatever the last message was.

You should probably also put a RETURN statement inside of your MONMSG DO-group so that statemants after the ENDDO aren’t executed. There are lots of other ways to take care of that, but a RETURN is straightforward and clear to anyone.

#!/bin/bash
# This is a SFTP script
success=0
sftp -oPort=6222 -oUserKnownHostsFile=/dev/null -oStrictHostKeyChecking=no User@TargetSys || success=$?<<EOF
cd folder1
put fileName
EOF
#End of script
exit $success

I am trying to capture the value error if any in success field.

How ever I am facing the issue that the script runs only the first line i.e. “sftp -b ……….” command and gives the value to the success field.
The rest of the commands are not executed.

The next issue that I am facing is how to capture this return value in my cl program.

At present my CL code is:

PGM

/* IF VARIABLES WERE SET PREVIOUSLY, REMOVE THEM SO THAT OUR +
ADDENVVAR COMMANDS WORK. */

DCL VAR(&QSCOMD) TYPE(*CHAR) LEN(200) +
VALUE(*BLANKS)
CHGVAR VAR(&QSCOMD) VALUE(‘ksh -x sftpscript.sh’)

/* SET THE COMMAND OUTPUT TO NONE, AND TELL QSH TO ISSUE +
ESCAPE MESSAGES FOR ERRORS. */

ADDENVVAR ENVVAR(QIBM_QSH_CMD_OUTPUT) VALUE(NONE) +
LEVEL(*JOB) REPLACE(*YES)
ADDENVVAR ENVVAR(QIBM_QSH_CMD_ESCAPE_MSG) VALUE(Y) +
LEVEL(*JOB) REPLACE(*YES)
/* EXECUTE OUR QSHELL COMMAND */

STRQSH CMD(&QSCOMD)
MONMSG MSGID(QSH0000) EXEC(DO)
SNDPGMMSG MSGID(CPF9897) MSGF(QCPFMSG) MSGDTA(‘QShell +
command failed!’)
ENDDO
ENDPGM

You should be able to receive that message and access the exit status in the message data. It’s returned as a 4-byte binary field.

Tom

DanF