OnDemand User Group

Support Forums => z/OS Server => Topic started by: Pk2016 on January 20, 2017, 12:45:46 PM

Title: Load ID Format - Help
Post by: Pk2016 on January 20, 2017, 12:45:46 PM
Hi,

Can anyone direct me to the documentation of the updated load-id format in CMOD 9.5 .

Pre upgrade format (v8.5)
 LoadId(5559-11-0-10369FAA-17081-17081) File(/ars/tmp/67110863 (DD:INPUT- xxxx.xxxx.AFP)) InputSize(540349) OutputSize(144973) Rows(13) Time(3.7510) Appl(XXXX2AAC)

Post Upgrade :(v9.5)
 LoadId(5559-11-0-10381FAA-20161007000000-20161007000000-5562)File(/ars/tmp//33556151.000001579F7B8B58) InputSize(211107) OutputSize(57367) Rows(5) Time(0.1723) Appl(XXX2AAC) InputFileSize(-1)


ALso in 9.5 ,  its not showing the input file name(underlined above)  used for the load  instead shows ars/tmp/.......

Would like to know if that is its supposed to be with the new upgrade or what we have is incorrect.

upgraded from 8.5 to 9.5( Zos)

Thank you

Title: Re: Load ID Format - Help
Post by: Greg Ira on January 20, 2017, 01:21:14 PM
The load ID format can be found in the V9.5 Administration guide under ARSADMIN -L parameter description.
Input file name looks consistent with what we get in our load messages.
Title: Re: Load ID Format - Help
Post by: Pk2016 on January 20, 2017, 01:43:25 PM
Thank you Greg Ira,that helped.

Still trying to figure out the File name change.
Title: Re: Load ID Format - Help
Post by: Justin Derrick on January 22, 2017, 03:25:28 AM
The filename in /ars/tmp looks like a bug.  It should be the path and filename where the original file was listed, not where the temporary file lives.

The Load ID hasn't changed much.  The old format was:

Code: [Select]
5559-11-0-10369FAA-17081-17081AppGroupID-StorageSet-0-DocNamePrefix-MinDate-MaxDate

The date format was either number of days since January 1st, 1970, or the number of seconds since January 1st, 1970, depending on the configuration of the Segment Date field in your Application Group.

And the new format isn't much different.
Code: [Select]
5559-11-0-10381FAA-20161007000000-20161007000000-5562
AppGroupID-StorageSet-0-DocNamePrefix-MinDate-MaxDate-ApplicationID

Where dates are now stored in YYYYMMDDHHMMSS format (Thats YearMonthDayHourMinuteSecond).  The only addition is the ApplicationID at the end, which refers to the internal numeric ID for the Application definition that was used to index/load the data.

There's also an article on the Doc_Name format on the CMOD wiki:  http://cmod.wiki/index.php/DOC_NAME

-JD.
Title: Re: Load ID Format - Help
Post by: Pk2016 on January 23, 2017, 08:03:42 AM
Thank You Dustin.

I agree with the filename . Will have to investigate further where that is picking from and why the input file name is not picked up.

Thanks again for the description of the Load iD Format. The "20161007000000" is actually the load date . It is same as the date the statements were loaded to ondemand. Was skeptical about why does it write  the timestamp twice.

Will go through the CMOD Wiki link.
Title: Re: Load ID Format - Help
Post by: Alessandro Perucchi on January 23, 2017, 09:18:06 AM
in the load id, the field corresponding to MinDate and MaxDate correspond in your load that you are trying to archive to the field that represent the "segment" flag in your application group (maybe a field called docdate).
And during the load "arsload" will look at the oldest date and newest date from your batch.
In your case, all documents have the date "20161007000000", so it is normal that MinDate = MaxDate = "20161007000000"
If you have a mix of dates, let say "20161001000000", "20161007000000", "20161011000000", the your load ID would look like :

5559-11-0-10381FAA-20161001000000-20161011000000-5562

since MinDate=20161001000000 and MaxDate = 20161011000000.

Regards,
Alessandro
Title: Re: Load ID Format - Help
Post by: Pk2016 on January 23, 2017, 10:55:05 AM
Thank you for the explanation Alessandro .