kindly please for advice with regards to the FileID. Anytime the file is being viewed and columns are allinged to be saved to the file under SYSUID, "vprint" command is used to save the view to the user member. All the time the file data in formatted view are truncated. I have revisited FileID setting and switch off the truncation to get the full file in formatted view saved for additional user analysis. Now, going across additional questionnaire where file size, format etc. needs to be filled in and I can not decode. When anyone skilled with "vprint" command and options to save the file data in formatted view or any other way to manage it, please respond to this query and I am more than happy to send more details to your check and advise. Thanks
Joined: 05 Mar 2007 Posts: 10 Location: Sydney, Australia
I was exactly in your situation last year some time when one of my friends required the complete data in column format. Our master file consisted of almost 5000 fields and imagine that.
So, as I found succesfully that fileaid cannot get the VPRINT more than 133 bytes and got confirmed by below documentation, I went in the other way round. Please see if this is useful for you.
1) Take the regular cobol layout and create a copy version of it. Lets say CPY1 is master layout and CPY2 is second version of same layout
2) Ensure that you do change all non-alphanumeric/numeric variables into DISPLAY numeric variables (meaning S9(09)V99 COMP-3 to +9(09).99)
3) Go to Fileaid Option 9.
4) Give source layout as CPY1 and target layout as CPY2
5) Create a temporary file FILE2 with record length of CPY2 (as we modified the type, length would increase a lot)
6) Give Original master file as input and FILE2 as output dataset
7) Execute the transformation. (This basically does MOVE CORRESPONDING in COBOL or something similar)
If you want to get a space between each field, write a quick edit macro which can insert a line
FILLER PIC X(01) VALUE ' '.
after every variable declaration
and, do the transformation and you should be getting the data in column format.
Issues in this approach are:
1) REDEFINES can have problems, so you have to handle few errors manually as you keep trying
2) Data exceptions, if there is any invalid data in the fields you are referring to, you will have a S0C7 and fileaid beautifully won't tell which field have the problem, which again is manual effort. (Fortunately, it tells you the record number which have the issue )
I know this is a little crude approach, but, I could not find any quicker solution at that point of time. If any one else know any better approach, ideas are highly appreciated.
Hope this helps!
==Extract from Fileaid Batch documentation==
The VPRINT report output width is 132 characters. The report format includes spaces
separating the fields. When the VPRINT output exceeds the report width, File-AID writes
the VPRINT DATA TRUNCATION informational message, VP001-Data truncation
occurred while processing VPRINT request to the SYSPRINT log. Use the FIELDS
parameter to specify which fields to include in the VPRINT output. See “FIELDS” on page
==End of extract==