|
View previous topic :: View next topic
|
| Author |
Message |
Furion
New User
Joined: 27 Nov 2007
Posts: 14
Location: China
|
|
|
|
Hi all,
Could anyone tell me how to convert one U format file to FB format?
I have one undefined format file and I need to convert it to some FB format. Is there anyway?
Thx in advance |
|
| Back to top |
|
 |
mnnarayankar
New User
Joined: 21 Jan 2008
Posts: 23
Location: bangalore
|
|
|
|
I think,
The U formate is called unformated file.
If u consider the unformated file it contains all system related symbols or character which is understood by system.
Example of UNFORMATED file is nothing but our load module or object module member ( or file). Nad i think it is impossible to read all system related character. and it is variable block VB type.
For u r simplicity open loadlib with 'i' option instead u open in 'e' option. |
|
| Back to top |
|
|
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello,
If you post some of the content (and describe just what it is) of the "U" file, we can probably offer suggestions on how to write the data to an FB file. |
|
| Back to top |
|
|
enrico-sorichetti
Superior Member
Joined: 14 Mar 2007
Posts: 10873
Location: italy
|
|
|
|
| Quote: |
| The U formate is called unformated file. |
as already said in other posts U means undefined...
for FB files the lrecl and blksize are stored in the VTOC
( rough approach ... to keep things simple )
the physical read and logical deblockig will be done by data management based on those values
for VB files same as above
the lrecl is less important because
the physical read and logical deblockig will be done by data management
but the logical deblocking will be based on the RDW or RDF
( record definition word/record definition field)
for U files
the data management will simply take care of the physical read
and the whole block read will be passed back to the application program
If You care about the details here they are for assembler
You have to issue a read for the maximum blksize expected,
after the read one of the control blocks will contain the residual length ( not read stuff )
( I do not right now remember which... decb/csw)
the difference between the blksize length requested and the residual length
will give the block/record lenght
the records of a load module are not unformatted...
if they were nobody would be able to understand thir content  |
|
| Back to top |
|
|
|
|
