Re: RCVMSG hell...

[Jeff Crosby <jlcrosby@xxxxxxxxxxxxxxxx>]

Another possibility is not looking for those messages at all, but simply get
a list of the file members afterward.

TAATOOLS has a RTVMBRLST command and I'm sure there's an API for that.  This
presumes there were no members beforehand (or you got a list of the
'befores').  If there could have been members beforehand, this is probably
more work.



On Fri, Aug 19, 2011 at 3:21 AM, Booth Martin <booth@xxxxxxxxxxxx> wrote:

> Would the information you want be in the FTP log file in your OUTPUT file?
>
> fwiw; probably not useful for what you are describing,
>
> http://www.martinvt.com/Code_Samples/FTP_Utility/ftp_utility.html
>
> (With minimal tweaking, it can also run silent.)
>
>
> On 8/18/2011 11:59 PM, sjl wrote:
> > I am prototyping a program which does batch FTP.
> >
> > [ Cannot use FTPAPI...  ;-( ]
> >
> > 1) Bound CL program A calls RPGIV program B which builds the FTP script
> in
> > the source file.
> >
> > 2) Then program A calls bound CL program C, which overrides INPUT to the
> > member containing the FTP script built by program B.  The FTP script uses
> > MGET FILEXXX.* to get multiple files beginning with the characters
> "FILEXXX"
> > from the remote server.
> >
> > Example of the remote files being retrieved:
> > FILEXXX.1.A000001
> > FILEXXX.2.A000002
> > ...
> >
> > The result of the MGET is a file named FILEXXX in the current library,
> with
> > two members:
> > A000001 and A000002.
> >
> > So far, so good.
> >
> > In order to capture the file and member names received, I want to use the
> > RCVMSG command in CLLE program C to retrieve the completion messages that
> > appear in the job log.
> >
> > The specific messages in which I am interested are the CPC7301 and
> CPC7305
> > messages issued by the FTP processor, but I cannot seem to get it to work
> > properly - I never receive these completion messages in my RCVMSG loop:
> >
> > CPC7301    Completion              00   08/18/11  20:11:16.133800  QDDCPF
> > QSYS        0567     QC2SYS      QSYS        *STMT
> >                                       To module . . . . . . . . . :
> QC2SYS
> >                                       To procedure  . . . . . . . :
> system
> >                                       Statement . . . . . . . . . :   6
> >                                       Message . . . . :   File FILEXXX
> > created in library SJLFTP.
> >
> > CPC7305    Completion              00   08/18/11  20:11:16.157120
>  QDDCPFM
> > QSYS        005B     QC2SYS      QSYS        *STMT
> >                                       To module . . . . . . . . . :
> QC2SYS
> >                                       To procedure  . . . . . . . :
> system
> >                                       Statement . . . . . . . . . :   6
> >                                       Message . . . . :   Member A000001
> > added to file FILEXXX in SJLFTP.
> >
> > CPC7305    Completion              00   08/18/11  20:11:16.264264
>  QDDCPFM
> > QSYS        005B     QC2SYS      QSYS        *STMT
> >                                       To module . . . . . . . . . :
> QC2SYS
> >                                       To procedure  . . . . . . . :
> system
> >                                       Statement . . . . . . . . . :   6
> >                                       Message . . . . :   Member A000002
> > added to file FILEXXX in SJLFTP.
> >
> > Does anyone have a working example of code which does something similar?
> >
> > Regards,
> > SJL
>
> --
> Booth Martin
> 802-461-5349
> http://www.martinvt.com
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.