1. Forum
  2. USENET
  3. comp.sys.unisys

  • Starting a program from WFL with TADS

    From CR@chaianju@gmail.com to comp.sys.unisys on Thu Sep 22 12:19:11 2022
    From Newsgroup: comp.sys.unisys

    I should know this, but have forgotten how to do it. The following is the job. Where/how do I specify that the program is to be run with TADS ?
    From CANDE, it is easy to do a RUN OBJECT/DIRSCANNER;TADS.

    I need to pass various options to the program which has been compiled with TADS, which is why I am running it from the WFL.

    00000100BEGIN JOB J;
    00000200BDNAME=CSR;
    00000310RUN OBJECT/DIRSCANNER ON WORKPACK; 00000400 DATABASE BLPACKDB(TITLE=BLPACKDB ON PACK);
    00000500DATA OPTIONS
    00000600PACKNAMES PROD
    00000700COMPAREDATE -1
    00000800?
    00000900END JOB.

    Thanks
    Chai
    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From Paul Kimpel@paul.kimpel@digm.com to comp.sys.unisys on Thu Sep 22 17:56:31 2022
    From Newsgroup: comp.sys.unisys

    On 9/22/2022 12:19 PM, CR wrote:
    I should know this, but have forgotten how to do it. The following is the job. Where/how do I specify that the program is to be run with TADS ?
    From CANDE, it is easy to do a RUN OBJECT/DIRSCANNER;TADS.

    I need to pass various options to the program which has been compiled with TADS, which is why I am running it from the WFL.

    00000100BEGIN JOB J;
    00000200BDNAME=CSR;
    00000310RUN OBJECT/DIRSCANNER ON WORKPACK;
    00000400 DATABASE BLPACKDB(TITLE=BLPACKDB ON PACK);
    00000500DATA OPTIONS
    00000600PACKNAMES PROD
    00000700COMPAREDATE -1
    00000800?
    00000900END JOB.

    Thanks
    Chai

    The same way you do in CANDE. TADS is a Boolean task attribute, so it
    can go anywhere a task attribute can go -- after the RUN statement and
    before the DATA line, e.g,

    00000310RUN OBJECT/DIRSCANNER ON WORKPACK;
    00000350 TADS;
    00000400 DATABASE BLPACKDB(TITLE=BLPACKDB ON PACK);
    00000500DATA OPTIONS

    Specifying just "TADS;" is the same as specifying "TADS=TRUE;"

    When the program runs, TADS is going to need to connect to either a
    remote station or an IDE (like PWB), so you may need to specify the
    STATION or STATIONNAME attribute or supply file equation for the port file.

    Paul


    --- Synchronet 3.21d-Linux NewsLink 1.2
  • From CR@chaianju@gmail.com to comp.sys.unisys on Fri Sep 23 05:53:16 2022
    From Newsgroup: comp.sys.unisys

    On Thursday, September 22, 2022 at 8:56:32 PM UTC-4, Paul Kimpel wrote:
    On 9/22/2022 12:19 PM, CR wrote:
    I should know this, but have forgotten how to do it. The following is the job. Where/how do I specify that the program is to be run with TADS ?
    From CANDE, it is easy to do a RUN OBJECT/DIRSCANNER;TADS.

    I need to pass various options to the program which has been compiled with TADS, which is why I am running it from the WFL.

    00000100BEGIN JOB J;
    00000200BDNAME=CSR;
    00000310RUN OBJECT/DIRSCANNER ON WORKPACK;
    00000400 DATABASE BLPACKDB(TITLE=BLPACKDB ON PACK);
    00000500DATA OPTIONS
    00000600PACKNAMES PROD
    00000700COMPAREDATE -1
    00000800?
    00000900END JOB.

    Thanks
    Chai
    The same way you do in CANDE. TADS is a Boolean task attribute, so it
    can go anywhere a task attribute can go -- after the RUN statement and before the DATA line, e.g,

    00000310RUN OBJECT/DIRSCANNER ON WORKPACK;
    00000350 TADS;
    00000400 DATABASE BLPACKDB(TITLE=BLPACKDB ON PACK);
    00000500DATA OPTIONS
    Specifying just "TADS;" is the same as specifying "TADS=TRUE;"

    When the program runs, TADS is going to need to connect to either a
    remote station or an IDE (like PWB), so you may need to specify the
    STATION or STATIONNAME attribute or supply file equation for the port file.

    Paul
    Yes Paul, you are correct. I was just putting the "TADS" in the wrong spot with the START statement. Thanks.
    --- Synchronet 3.21d-Linux NewsLink 1.2