Results 1 to 2 of 2

Thread: datasets

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

    Default 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
    43
    Rep Power
    0

    Default 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

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

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

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255