Re: Setting A Hex Value in COBOL

In article <0sk7i.362283$2Q1.84574@xxxxxxxxxxxx>,
gary <garyinri@xxxxxxxxx> wrote:
DD,

Program was last modified on 6-8-1994 and probably was originally developed
in the 80's. No date handling in the code so no Y2K remediation was needed.

Wow... and they still managed to find the source code? Good for them,
I've worked in far too many places where stuff gets moved around and the
system becomes closer than it should be to OCO.

Yes, the FF an NL do represent the codes for a NewLine and a FormFeed. As
for the "3-digits", I was referring to the 229, not the E5.

Well... win some, lose some. It might be interesting to find out what the
various codes do, just for laffs.


The reason I was trying to gather a little info first was that we have to
submit requests to our DBA group to get something complied and copied.

Now I'm lost again. I'm familiar with the necessity for (group) to have
responsibility for moving something from Development to Test to Prod, and
Great Magicks blessed by many of the High Ones needed to do so... but are
you saying that when you need any sort of compile the DBA has to do it?

There are times that things don't get turned around too quickly, so I'm
trying to minimize the number of requests I need to make.

This sounds like something back from Ye Oldene Dayse... a programmer is
allowed two (or more or less) compiles per day because those CPU cycles
cost big money and all that. What I'm hearing here is that you get some
code, put your mods in, submit a request to the DBA to compile, get a 12
back because you fat-fingered CH-NL into CH0NL, change the '0' to a '-',
submit a request to a DBA to compile, get a 12 back because you typo'd
PERFORM into PERFROM, change the code, submit a request...

I wonder what Productivity Improvement Structures and Steps will be
introduced next... maybe they'll have you work on coding sheets,
desk-check things to death and submit your pads to the card-punch girls to
be keyed in.

But yes, at this
point, I plan on just throwing the code out there and testing it with a
"let's go see" run.

That's the spirit... if things are as bad as I described above I'd be
happy to email you generic compile-JCL, invoking IGYCRCTL and HEWL... all
you'd have to do is find out what libraries they have hidden such
treasures in... and hope that you're not RACF'd out.

DD
.

Quantcast