MVSFORUMS.com

nbdtrjk1 · Beginner Joined: 12 Apr 2007 Posts: 76 Topics: 41

Hi All,
I have VB file length of 32000 bytes which has 100 records, 1st and 2nd record length is 100 bytes. 3rd and 7threcord length is 3000 bytes.

My requirement is...How to identify the length of the each Record in that VB file. Is it possible to read through COBOL and get the record length? or give me some alternate solution.
Or using RDW do something?

dbzTHEdinosauer · Posted: Tue Jun 26, 2007 4:41 am Post subject: a COBOL solution

Not exactly profi stuff, but:

Compile with the NOSSRANGE option.

Define INPUT-FILE FD with record length 1 to 32000.

define RECORD as

dbzTHEdinosauer · Posted: Tue Jun 26, 2007 4:45 am Post subject:

or using SORT

[code:1:061caa2a4b]
INREC FIELDS=(1,4, unedited RDW
1,2,BI,TO=ZD,LENGTH=5, display RDW length in decimal
C
_________________
Dick Brenholtz
American living in Varel, Germany

jajularamesh · Beginner Joined: 14 Apr 2006 Posts: 87 Topics: 33

You can read the record and get the information

Declare the FD section as given below

FD ACCOUNT-IN
DATA RECORD IS ACCOUNT-IN-RECORD
RECORDING MODE IS V
RECORD IS VARYING IN SIZE FROM 1 TO 1939 CHARACTERS
DEPENDING ON ACCT-RECORD-SIZE.

Each time you read the record the length of the record is captured in ACCT-RECORD-SIZE

Please let me know if you want further details

Regards,
Ramesh

jajularamesh · Beginner Joined: 14 Apr 2006 Posts: 87 Topics: 33

dbzTHEdinosauer,

Compile with the NOSSRANGE option.

I couldn't understand what you are trying to do convey from this and i guess this is no way related to the question asked.

Correct me if my question is wrong

Regards,
Ramesh

kolusu · Posted: Tue Jun 26, 2007 8:06 am Post subject:

dbzTHEdinosauer · Posted: Tue Jun 26, 2007 8:14 am Post subject:

jajularamesh,

your solution is much better, mine was a 'stone wheels & knives' approach.

as kolusu said, I wanted to avoid an abend as I strolled backwards from the start of the record.
_________________
Dick Brenholtz
American living in Varel, Germany

jajularamesh · Beginner Joined: 14 Apr 2006 Posts: 87 Topics: 33

Kolusu,

Actually nbdtrjk1 wants to capture the length of each record.

For this if i am not wrong we have to define the FD section in this way

RECORD IS VARYING IN SIZE FROM 1 TO 1939 CHARACTERS
DEPENDING ON ACCT-RECORD-SIZE.

where after each read length of the record is captured in ACCT-RECORD-SIZE

so this can be directly achieved right

Regards,
Ramesh

kolusu · Posted: Tue Jun 26, 2007 8:16 am Post subject:

jajularamesh,

If you read DBz's solution it also gives you the length of each record from the VB File but a different process. Your solution also works. OP can choose whichever solution he is comfortable with

Kolusu
_________________
Kolusu
www.linkedin.com/in/kolusu

jajularamesh · Beginner Joined: 14 Apr 2006 Posts: 87 Topics: 33

dbzTHEdinosauer,

Actually i am trying to understand what you gave there.

i have been working with VB files most frequently these days so i thought we can directly aceive this.

Sorry, don't take me wrong

Regards,
Venkata Apparao Jajula

dbzTHEdinosauer · Posted: Tue Jun 26, 2007 8:38 am Post subject:

jajularamesh,

the record description entry in the FD section actually is an area that 'floats' within the file buffer. If you look at a compiler listing, the 01 level is on a register. After each READ or WRITE, the ops-sys increments the register and the next record area in the buffer is made available.

For variable length records the VLI is the two characters in front of each record addressed in the FD record area. But, COBOL does not make that area definable, though you can access it by using an index and addressing the -2 and -1 offset to the Record Area.

I have not messed with QSAM (or VSAM) for about 20 years and did not bother to keep up with the FD DEPENDING ON clause, which you very eloquently provided as a solution.

I imagine COBOL will eventually not allow addressing the buffer directly. This is one of the reasons for the work-area option on I/O's. keeping COBOL programmers out of the buffer

as I said earlier, a 'stone wheels & knives' solution. But what do you expect from a dinosaur?
_________________
Dick Brenholtz
American living in Varel, Germany