Data Replication 2
Results 1 to 2 of 2

Thread: datasets

  1. #1
    lsabster is offline Junior Member
    Join Date
    Oct 2006
    Posts
    29
    Rep Power
    0

    datasets

    //JCBACCNT EXEC PGM=IKJEFT01,DYNAMNBR=30,PARM='NAVCMD'
    //SYSEXEC DD DSN=ISV.AC5010.USERLIB,DISP=SHR
    //SYSUDUMP DD SYSOUT=*
    //SYSOUT DD SYSOUT=*
    //SYSPRINT DD SYSOUT=*
    //SYSTSPRT DD SYSOUT=*
    //SYSTSIN DD DUMMY
    //SYSIN DD DSN=TSCBS.CALLDOS.INPUT2,DISP=SHR



    During the run of this job, the following datasets are allocated. I would like to make the following datasets unique per job in the case that multiple jobs (using above JCL) are active at the same time:

    ISV.AC5010.TMP.NAVLOG
    ISV.AC5010.TMP.LG000001 ISV.AC5010.TMP.LG000153

    How can we make the datasets unique?

  2. #2
    ussupport1 is offline US Support
    Join Date
    Sep 2006
    Posts
    49
    Rep Power
    0

    datasets

    ISV.AC5010.TMP.NAVLOG

    This data set is the default log file for what is called internally in our configuration as the default NAV binding. It is written to when certain execution is performed locally on the ZOS system for definitions under the NAV binding(e.g. NAVCMD --> execute DATASOURCE). In the binding you can specify the foramt you want to use for this file. Editing the binding via Studio is the best place to see this under DEBUG. For instance, a format of ISV.AC5010.TMP.NAVLOG%i will add a versioned number to the end of the file name. Two separate sessions executing NAVCMD will create their own unique log file. This parameter must be used with caution since the number of places for the increment can cause the file to be named differently. We reserve only eight positions for the node after the "TMP.". The one hundreth iteration of the log file would cause the file to be named ISV.AC5010.TMP.AVLOG100. So if you had a job to clean these files up using the wildcard node ISV.AC5010.TMP.NAVLOG* this file would be overlooked.


    ISV.AC5010.TMP.LG000001 ISV.AC5010.TMP.LG000153

    These files are created as a temporary log file when operations against the default file cannot be performed due to locking or security. They are no longer in use after the process disconnects and can be removed. If these files are being created frequently you might want to look into the permisions on the HLQ node of the log files to see if an ajustment neds to be made.
    To Find Out more About Attunity Technology:
    Attunity
    or:
    Contact Us

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •