From: Pete Dashwood on

<docdwarf(a)panix.com> wrote in message news:emsgci$spv$1(a)reader2.panix.com...
> In article <4vdr12F1botahU1(a)mid.individual.net>,
> Pete Dashwood <dashwood(a)removethis.enternet.co.nz> wrote:
>>I have a question, please, Doc.
>
> [snip]
>
>>If the JCL specifies a block size of 27990 (nicely divisible by 30, 933
>>times), and the COBOL program is specifying a block/record size of 32767,
>>wouldn't this be likely to cause an IO error when the dataset is opened?
>
> I thought there would be some kind of error as well, Mr Dashwood, hence my
> testing... but both of our thinkings appear to be contrary to Mr Morris'
> assertion that 'For FB code the maximum size 01 level expected for the FD
> and RECORD 0 in addition to BLOCK 0 and the actual record length will be
> determined at run time. Unfortunately this only works for INPUT.'
>
> I posted code which I believed was in accordance with this - it is a new
> technique for me and I'm not quite sure I got it right - and, likewise,
> posted the results (an ABEND). If there's something else I should be
> doing then, by all means, post the code - both COBOL and JCL - and I'll be
> more than happy to compile it and show the results.
>
> DD

As I don't have access to this environment I can't do it myself, but I'd be
very interested to see what happens if the Picture of the 01 following the
FD was made the same as the LRECL size...

Not wishing to impose, but perhaps, if you had time...? (all other things
remaining as you have them...)

Pete.


From: Michael Mattias on
> --begin quoted text:
>
> I think I didn't explain my problem well. Maybe it'll be better with
> an example. Let's say, I have file called TESTA. TESTA doesn't always
> have the same LRECL. Sometime TESTA will be defined in the JCL with
> LRECL=30. Other times, it will be have LRECL=70. And so on. My
> problem is how should TESTA be represented in FD?
>
> --end quoted text

Sorry to be jumping in so late, and I apologize if this has already been
suggested, but the answer is, "TESTA should not require definition in a
COBOL FD."

Add an IDCAMS, IEBGENER or synsort/dfsort job step prior to this program to
copy the file to a DISP=NEW (temp?) dataset ... with LRECL and BLKSIZE which
***IS*** a known constant (in this case, probably VB) and therefore *can* be
represented in a COBOL 01/FD. These utility programs should handle the
multiple possible input formats transparently.

MCM













From: Anonymous on
In article <4vf1ffF1c13jbU1(a)mid.individual.net>,
Pete Dashwood <dashwood(a)removethis.enternet.co.nz> wrote:
>
><docdwarf(a)panix.com> wrote in message news:emsgci$spv$1(a)reader2.panix.com...
>> In article <4vdr12F1botahU1(a)mid.individual.net>,
>> Pete Dashwood <dashwood(a)removethis.enternet.co.nz> wrote:
>>>I have a question, please, Doc.
>>
>> [snip]
>>
>>>If the JCL specifies a block size of 27990 (nicely divisible by 30, 933
>>>times), and the COBOL program is specifying a block/record size of 32767,
>>>wouldn't this be likely to cause an IO error when the dataset is opened?

[snip]

>> I posted code which I believed was in accordance with this - it is a new
>> technique for me and I'm not quite sure I got it right - and, likewise,
>> posted the results (an ABEND). If there's something else I should be
>> doing then, by all means, post the code - both COBOL and JCL - and I'll be
>> more than happy to compile it and show the results.
>
>As I don't have access to this environment I can't do it myself, but I'd be
>very interested to see what happens if the Picture of the 01 following the
>FD was made the same as the LRECL size...

Therein lies the difficulty, Mr Dashwood... as I understand the original
poster's request the LRECL of TESTA changes from one run to the next;
there is no *the* LRECL size. Once again, from
<http://groups.google.com/group/comp.lang.cobol/msg/e2bd0f47c45850c8?dmode=source>

--begin quoted text:

TESTA doesn't always have the same LRECL. Sometime TESTA will be defined
in the JCL with LRECL=30. Other times, it will be have LRECL=70. And so
on. My problem is how should TESTA be represented in FD?

--end quoted text

DD

From: Anonymous on
In article <Rctkh.2714$sR.1230(a)newssvr29.news.prodigy.net>,
Michael Mattias <mmattias(a)talsystems.com> wrote:
>> --begin quoted text:
>>
>> I think I didn't explain my problem well. Maybe it'll be better with
>> an example. Let's say, I have file called TESTA. TESTA doesn't always
>> have the same LRECL. Sometime TESTA will be defined in the JCL with
>> LRECL=30. Other times, it will be have LRECL=70. And so on. My
>> problem is how should TESTA be represented in FD?
>>
>> --end quoted text
>
>Sorry to be jumping in so late, and I apologize if this has already been
>suggested, but the answer is, "TESTA should not require definition in a
>COBOL FD."

Now, now, Mr Mattias... saying 'This question is invalid' isn't always the
best way to get a good grade on one's homework assignment, is it?

('Given the initial masses, positions and velocities and using Newton's
Law of Gravity and Laws of Motion, determine the subsequent motions of
three bodies. Use both sides of the paper, if necessary.')

DD
From: Michael Mattias on
<docdwarf(a)panix.com> wrote in message news:emtrt6$an3$1(a)reader2.panix.com...
> In article <Rctkh.2714$sR.1230(a)newssvr29.news.prodigy.net>,
> Michael Mattias <mmattias(a)talsystems.com> wrote:
>>> --begin quoted text:
>>>
>>> I think I didn't explain my problem well. Maybe it'll be better with
>>> an example. Let's say, I have file called TESTA. TESTA doesn't always
>>> have the same LRECL. Sometime TESTA will be defined in the JCL with
>>> LRECL=30. Other times, it will be have LRECL=70. And so on. My
>>> problem is how should TESTA be represented in FD?
>>>
>>> --end quoted text
>>
>>Sorry to be jumping in so late, and I apologize if this has already been
>>suggested, but the answer is, "TESTA should not require definition in a
>>COBOL FD."
>> ... [straightforward solution to problem]...

> Now, now, Mr Mattias... saying 'This question is invalid' isn't always the
> best way to get a good grade on one's homework assignment, is it?

You sure have a strange way of saying, "Damn, I wish I had thought of that!"

(See also: today's post from yours truly in the "interview" thread re what
consultants are actually paid to do).

MCM