problem while uploading log file to mainframe

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

I have a log file on windows system. looks like this -

1363518*D*20091209*
1363477*A*20091209*
1363470*A*20091209*
1363465*A*20091209*20091214
1363461*A*20091209*
1363455*A*20091209*20091214
1245292*A*20100604*
1245217*A*20100604*
R0000115160*A*20100604*
R0000115045*A*20100604*
R0000115754*A*20100604*20100607
R0000115375*A*20100604*20100607
R0000114925*A*20100604*
R0000114885*A*20100604*

When i am downloading into mainframe, it is getting downloaded in the below fashion with LRECL=80

1363518*D*20091209*1363477*A*20091209*1363470*A*20091209*1363465*A*20091209*200
912141363461*A*20091209*1363455*A*20091209*200912141245292*A*20100604*1245217*A
*20100604*R0000115160*A*20100604*R0000115045*A*20100604*R0000115754*A*20100604*
20100607R0000115375*A*20100604*20100607R0000114925*A*20100604*R0000114885*A*201
00604*

I want the file the way it looks in windows system (mentioned above). Did searched on forum, but didnt find any topic that suits to my requirement.

Here are the batch FTP commands used to download the file.

userid
password
CD StatusFile
locsite RECFM=F FWFriendly WRAPrecord
get logfile.log 'tt.tx.#670.test.log(+1)'
dir
quit

Can anyone guide me?
Thanks

superk · Posted: Thu Aug 26, 2010 7:43 pm

Could you post a hex dump of the ASCII file contents, for what you think should be a few records?

Something like this, as an example:

Robert Sample · Posted: Thu Aug 26, 2010 7:45 pm

Does the log file look like your post in NOTEPAD or are you using a special program to look at it? The behavior you are seeing is consistent with a file that does not contain end-of-record markers (cr/lf on Windows).

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

Superk, Hex format looks like this

PeterHolland · Posted: Fri Aug 27, 2010 5:37 pm

What kind of logfile would this be? The windows logfile as seen in event viewer?

Robert Sample · Posted: Fri Aug 27, 2010 5:44 pm

This file is not a text file -- which has CR/LF (X'0D0A') at the end of each record. It appears there is an X'FC' at the end of the data record -- so you may need to manually deblock the data.

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

This is kind of log file that shows event status for one of the clients. we dont have event viewer.

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

there is no other way other than manual separation, becasuse this is going to run on daily basis, so checking options to automate the process.
This is a .log file, not .txt file.

Robert Sample · Posted: Fri Aug 27, 2010 6:25 pm

By manual, I mean you could write a program in the language of your choice to read each 80-byte record, split it into records based on the X'FC' record delimiter, and write those records into another file. As far as I am aware, there's nothing in z/OS to help you -- although you might check with the SORT people to see if they have a way to handle this data.

superk · Posted: Fri Aug 27, 2010 6:41 pm

Robert, this is driving me nuts. Where do you see the x'FC' character? I keep seeing the x'5C' (*).

Robert Sample · Posted: Fri Aug 27, 2010 7:11 pm

Kevin, you're right -- I was misreading the hex values. Serves me right for looking at a screen before I drink my coffee!

Bang_1, based upon my revisited look at the data -- unless you have a tool to create a text file from the log file, there is no practical way for a mainframe to deal with your data file as a production application.

superk · Posted: Fri Aug 27, 2010 7:29 pm

I still would've liked to have seen the actual, native, raw ASCII data in hex. I really can't tell what logically distinguishes one record from another, unless it's based strictly on the length of each logical record.

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

Thanks for the inputs...
This is what Iam doing now ---
1) Read each character on a record (lets say downloaded to LRECL of 32 file)
2) Go on caoncatinating each & every character until x'15' (which is EOL for this log file in this case)
3) Write the concatinated string on to output file
4) Repeat this process until 32 characters of a record
5) Repeat this process for the whole set of records

Let me know if ay improvements can be done to this process...

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

Its working with the above logic, thanks to all for your valuable inputs

dick scherrer · Posted: Mon Aug 30, 2010 7:55 pm

Hello,

If it works, i suppose all is well. . .

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

In my earlier post, i have posted how the file looks in HEX format without delimiters.

Log file is downloaded with LRECL of 32. Here is the snapshot of that file in HEX format in mainframe.. Now the file has X'15' on column #20 in line#1. This one used as reference to break the lines...

Few test cases were ran against the code, its breaking fine till now. We have another week of testing, and we will work on corrections, if it doenst break as expected....

dick scherrer · Posted: Tue Aug 31, 2010 8:09 pm

Hello,

You need to to make sure you use the code tag. . . The way you posted the most recent data was basically unreadable.

Originally there were x'0D0A' values that appear to have become x'15'. . . What caused this?

When i've sent data with x'0D0A' in the data, i get a record break. . .

I'm probably looking at something incorrectly, but it appears this is a moving target.

superk · Posted: Tue Aug 31, 2010 8:19 pm

Bang_1, you originally stated that this file originated on a Windows machine, which is one reason why I asked if you could post a hex dump of that data so we'd all know what it looks like as it exists in Windows.

Do you not know how to run a dump of data in Windows? It's relatively easy to do.

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

Dick, I will use CODE tag from next time onwards...
first i posted ASCII format of file on windows in 2 formats. One shows how it looks on windows, otherone how its in mainframe without delimiters, then superk posted the hex dump of mainframe without delimiters. I think you might have referring to this (X'ODOA').
Again I posted Hex dump on mainframe while I am developing the code on Tue Aug 31, 2010 12:51 pm. This one has the delimiter X'15', which is used as reference to break into lines.... Hope Iam clear....

Superk, we dont have access to windows ftp box apart from batch ftp thru JCL. So didnt i posted the windows dumps.

dick scherrer · Posted: Wed Sep 01, 2010 7:40 pm

Hello,

You might do an experiment changing the x'15' values to x'0D' before the upload. . .

Bang_1 · New User Joined: 08 May 2009 Posts: 39 Location: Bangalore

Dick, We dont have any permission apart from download on Windows FTP box.

dick scherrer · Posted: Wed Sep 01, 2010 8:35 pm

Hello,

Suggest you make a copy of the log file on a pc where you do have the ability to work and then run this experiment.

If this solves the problem, present to your management that there is a solution that needs to be implemented on the restricted system. If this does not work, we continue