Rob, I don't think IBM will accept your request for change. IBM's policy for output files is never to change the file format, and put new fields on the end, specifying LVLCHK(*NO). Several releases ado, IBM added two new fields to QADSPOBJ (the output file for DSPOBJD): ODSSZU P 10.0 Save size in units ODSBPU P 10.0 Save size multiplier You are advised to multiply these numbers together to get the correct answer. Al Al Barsa, Jr. Barsa Consulting Group, LLC 400>390 914-251-1234 914-251-9406 fax http://www.barsaconsulting.com http://www.taatool.com firstname.lastname@example.org Sent by: To: email@example.com midrange-l-admin@mi cc: drange.com Subject: DSPOBJD limitation 01/04/02 09:37 AM Please respond to midrange-l Ok folks, I am going to submit a design change request form. I want to know, after I do so, who I'll have to watch out for in dark alleys. We have individual objects on our system that are bigger than 10GB. When you do a DSPOBJD to an outfile the outfile returns 10 nines. I need the size of the field ODOBSZ increased. Frankly, since it is a packed field, adding one more digit would be painless, but that still wouldn't cut it - each of these objects is 1/3 terabyte, or 12 digits. I figure that it is better to make everyone go through a little suffering in the short term than to have IBM add a new field and have to use SQL for the following SELECT ODLBNM, ODOBNM, ODOBTP, ODOBAT, case when odobsz <> 9999999999 then odobsz else newfield end as Size, , ODOBTX from ROB/BIGOUT In case you are wondering how we got such huge files on our system - We are using Tivoli/Adstar to backup our PC's to our 400. From there to tape. We do restores on a frequent basis so this works out great for us. I am hoping that since this uses a crapload of disk, and some hefty tape drives, on the biggest 400 in the state then maybe I'll have a little pull with IBM. Rob Berendt -- "They that can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety." Benjamin Franklin _______________________________________________ This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l or email: MIDRANGE-Lfirstname.lastname@example.org Before posting, please take a moment to review the archives at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.