|
View previous topic :: View next topic
|
| Author |
Message |
William Thompson
Global Moderator
Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ
|
|
|
|
| Quote: |
| So wen i tried writing the entire input log file to an output FB file these records were displayed as follows |
Just what did you use to write "the entire input log file to an output FB file"? |
|
| Back to top |
|
 |
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
| Ya am sure about that |
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
| I tried to copy the input log file to the output FB file using IEBGENER as well as SORT. I have given the job details earlier for this post. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| Ya am sure about that |
ridiculous remark
the crippled output is the result of processing a VB dataset as a FB dataset...
do You realize it or not ?
all the data is junked up!
browse the output dataset with hex on and You will see that before the readable data there will be four bytes containing the length of the data itself up to the next 4 |
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
I have checked the file as u said, the 1st four bytes contain the log data and not the length.
I have checked it properly and thats why i said am sure that its not a VB file |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
if You are sure then everything should work
and You have no reason at all to complain |
|
| Back to top |
|
|
William Thompson
Global Moderator
Joined: 18 Nov 2006
Posts: 3156
Location: Tucson AZ
|
|
|
|
How about posting the HEX ON display of a display of
| Code: |
| NOTE: This session is executing on the z/OS V01R10M00 platform. |
? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
it would be more interesting an hex display of the output !
in the fist post there is a clear indication of many unprintable chars spread
around |
|
| Back to top |
|
|
Arun Raj
Moderator
Joined: 17 Oct 2006
Posts: 2481
Location: @my desk
|
|
|
|
| Quote: |
| This error field is shown in position 2 but when i search for 'ERROR:' string from position 2 its not found. |
Prasanya,
Did you try searching "ERROR:" at pos-3 given that you have an FBA input ?
omg, this thread has gone too far w/o making any progress.  |
|
| Back to top |
|
|
VVRAVINDRA
New User
Joined: 04 Aug 2008
Posts: 46
Location: Chennai
|
|
|
|
I'm sure my answer would look absurd compared to the master choices that you all have mentioned but I just wanted to try my luck out....
Please ignore/delete this post if it doesn't meet the standards....
Firstly, I copied the 4 lines of data from the input file provided by the Prasanya to a FBA 80 byte file (for testing)
Here are the contents of the i/p file:
| Code: |
***************************** Top of Data ******************************
----+----1----+----2----+----3----+----4----+----5----+----6----+----7--
1 THE SAS
SYSTEM 01:00 TUESDAY, FEBRUARY 2, 2010
NOTE: COPYRIGHT (C) 2002-2003 BY SAS INSTITUTE INC., CARY, NC, USA.
NOTE: SAS (R) 9.1 (TS1M3) |
And then I had a O/P file with length 79 and DCB=FB.
I tried the SORT option and here goes my sort card
| Code: |
SORT FIELDS=COPY
OUTFIL OUTREC=(1:1,79) |
Then i executed the job, and the output file looked the same as the input file...I did a SUPERC and found that the records were matching..
Once again my sincere apoligies if my answer is looking hasty or imappropriate.
Thanks,
Ravi |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
Ravi!
Your test is ok!
it might be biased that You did run it from data cut and pasted from the topic
and of a good/certain/sure origin
what we are still puzzling about is the goodness of the data in the TS environment
or at least of the understanding by the TS of its organization
the thing we are debating also is the ****ing  <output> dataset with all the data junked up! |
|
| Back to top |
|
|
Craq Giegerich
Senior Member
Joined: 19 May 2007
Posts: 1512
Location: Virginia, USA
|
|
|
|
| I wonder if the original file was FBA or VBA? |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| I wonder if the original file was FBA or VBA? |
how could You
I had told the TS to check, especially after having seen the <output> dataset
but the TS said he was sure and confirmed |
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
I have already mentioned its a FBA file and am sure about this. I do have a proper understanding if the system that am working in. Please keep in mind that its a log file created by SAS.
Do you need some kind of proof to be sure that its an FBA file?
Hi Arun,
I have already tried using position 3 but i dint get a match for 'ERROR:' |
|
| Back to top |
|
|
expat
Global Moderator
Joined: 14 Mar 2007
Posts: 8797
Location: Welsh Wales
|
|
|
|
Does SYNCSORT have SS capabilities
INCLUDE COND=(1,99,SS,EQ,C'ERROR') |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
| Prasanya wrote: |
I have already mentioned its a FBA file and am sure about this. I do have a proper understanding if the system that am working in. Please keep in mind that its a log file created by SAS.
Do you need some kind of proof to be sure that its an FBA file?
Hi Arun,
I have already tried using position 3 but i dint get a match for 'ERROR:' |
Yes, i would like to see some proof if it is a FBA file.
The SAS log is normally a VBA dataset. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
Please keep in mind that its a log file created by SAS.
|
the answers You got were because we kept that in mind
from the SAS manual
| Quote: |
SAS Log File
The SAS log file is a temporary physical file that has a DDname of SASLOG in both the SAS cataloged procedure and the SAS CLIST. In batch mode, the SAS cataloged procedure assigns default data control block (DCB) characteristics to this file as follows:
BLKSIZE=141
LRECL=137
RECFM=VBA |
repeat on
and that explain why..
the first sample (input) looks right,
the second sample (output) looks wrong
it' s what happens when You process a VB dataset with a FB dcb |
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
This is the datset information of the SAS log file
| Code: |
General Data Current Allocation
Management class . . : DEV Allocated blocks . : 2
Storage class . . . : DEV1000 Allocated extents . : 1
Volume serial . . . : 9SDS6D
Device type . . . . : 3390
Data class . . . . . : ADDDSORG Current Utilization
Organization . . . : PS Used blocks . . . . : 1
Record format . . . : FBA Used extents . . . : 1
Record length . . . : 255
Block size . . . . : 27795
1st extent blocks . : 2
Secondary blocks . : 300
Data set name type : SMS Compressible : NO
Creation date . . . : 2010/02/03 Referenced date . . : 2010/02/10
Expiration date . . : ***None***
|
|
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
| I tried copying the input file to a VB file as well and my output still looks similar to the previous output. |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
Looks FBA to me.
Now i would like to see the JCL allocation of this dataset. |
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
| This file is created by a third party production system so i cant view the JCL |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
Can you execute the following IDCAMS and show the output ?
| Code: |
// EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=A
//indd DD DSN= ... (describes the input data set)
//SYSIN DD *
PRINT -
INFILE(indd) -
DUMP -
COUNT(4)
/*
|
|
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
This was the 1st record in the spool.
| Code: |
0RECORD SEQUENCE NUMBER - 1
000000 000140C6 000000FF 81F1F139 8DE38885 40E2C1E2 40E2A8A2 A385941B 9EF0F17A *.. F.....11..T.. SAS S.......01:*
000020 F0F040E3 A485A284 81A86B40 C6858299 A48199A8 40F26B40 F2F0F1F0 787978FE *00 T......, F....... 2, 2010....*
000040 00C2D5D6 E3C57A40 C39697A8 99898788 A3404D83 5D40F2F0 F0F260F2 F0F0F340 *.BNOTE: C........ (.) 2002-2003 *
000060 82A840E2 C1E240C9 95A2A389 A3A4A385 40C99583 4B6B40C3 8199A86B 40D5C36B *.. SAS I........ I..., C..., NC,*
000080 40E4E2C1 4B78BA00 98D5D6E3 C57A40E2 C1E2404D 995D40F9 4BF1404D E3E2F1D4 * USA.....NOTE: SAS (.) 9.1 (TS1M*
0000A0 F35D78E4 06AFD389 838595A2 858440A3 9640C2C1 D5D240D6 C640C1D4 C5D9C9C3 *3).U..L....... .. AAAAAAAAAAAAAAA*
0000C0 C140D5C1 6B40E289 A38540F0 F0F5F3F4 F4F8F0F0 F14B78C7 00AAD5D6 E3C57A40 *A NA, S... 0053448001..G..NOTE: *
0000E0 E38889A2 40A285A2 A2899695 4089A240 85A78583 A4A38995 87409695 40A388 *T... ....... .. ......... .. .. *
|
Do you want the other records as well? |
|
| Back to top |
|
|
PeterHolland
Global Moderator
Joined: 27 Oct 2009
Posts: 2481
Location: Netherlands, Amstelveen
|
|
|
|
Looks like the first 4 bytes are a BDW and the second 4 bytes are the RDW (FF = 255 = lrecl)
So i conclude that the file is NOT a FBA file, and the supplier used the
wrong DCB values for the external SASLOG dataset. |
|
| Back to top |
|
|
Prasanya
New User
Joined: 04 Jun 2007
Posts: 34
Location: Chennai
|
|
|
|
Hi PeterHolland,
Thank you. Your conclusion was right, i confirmed with the third party system and they said that they have given file format as FBA inthe JCL creating the file.
But they will not be able to change it as the system has been in production for a few years. So is there any way to process this file |
|
| Back to top |
|
|
|
|
