• Subject: Re: CL variables in FTP commands
  • From: "Rick DuVall" <R_C_DuVall@xxxxxxxxxx>
  • Date: Thu, 25 Jan 2001 16:52:40 -0600

Hi Adam,

    The only way I know to do this is to alter the script source file on the
fly.


      OVRDBF     FILE(SOURCEIN) TOFILE(SrcLib/SrcFile) +
                   MBR(SrcMbr) LVLCHK(*NO) SECURE(*YES)

SrcMbr:
0001.04 userid password
0002.00 namefmt 1
0003.00 binary
0004.00 put /qdls/nadares/B201S001.003
0005.00 quit


      CALL       PGM(FIXFTPN)  (see below)

FSOURCEIN  UF   F   92        DISK
D                UDS
D  NAME                   1     12
ISOURCEIN  NS  01
I                                  1    6 2RECRD
I                                  7   12 0CHGDAT
I                                 13   15  PUT
I                                 13   92  RECORD
C                   READ      SOURCEIN                               30
C     PUT           IFEQ      'put'
C                   EXCEPT
C                   MOVE      *ON           *INLR
C                   END
OSOURCEIN  E
O                       NAME                42


    It is probably the hard way, but it solved the problem for me...

Regards
Rick

Rick@daaokc.com


> put mylib/myfile.mymbr mmddyyyy.raw
> put mylib/myfile.mymbr &CHGDATE.raw
>
> Can you do that? If not, is there another way to do this? Any input is
> appreciated.


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.