You could use an indirection in the I-Descriptor as well - use a SUBR which
then constructs a subroutine name and uses CALL @ syntax.For preference
I would resolve all these at the start of a user session in "one fell swoop"
and store the names in a dimensioned named COMMON block, using EQUATES
How do you make critical program changes for update routines against
your production databases? The creation of a separate account for
testing and training is a keystone for good program development. The
ingrained mindset needs to changed by you "the new kid" to take the shop
forward in basic softw
Not really a lot of work.
Once your tester program is written (should not be very big), your code
would change FROM something like:
CALL (ARG1, ARG2...)
To
CALL VERSION.TESTER()
CALL @(ARG1, ARG2...)
(or something like that)
Off the top of my head, this should not be too bad. J
hmmm this is a very interesting idea ..
thank you very much, its not as elegant as the path command but I think
it will do what I need
but if I understand it correctly there 2 things that have to be done
1. logic added to each program for this tester subroutine
2. the program would ha
any close to NC? I am very close to Raleigh and would be interested in
joining one and/or starting one if anyone in the NC area is interested.
dougc
---
u2-users mailing list
u2-users@listserver.u2ug.org
To unsubscribe please visit http://listserver.u2ug.org/
Write a simple tester subroutine that passes the name of the
original/standard program.
This subroutine reads a control record that uses your
user_id:"*CODETESTING" as the key (thus unique to each user). If not
found (which would be the case for most users), return the original
program name. If
Yeah we discussed the separate account idea 9we did that at my last job)
but here its more difficult and for ,whatever> reason people are against
it
Your other idea is not bad, but then we would have to change it in any
calling programs BUT I suppose that may be the best I can get out of
universe
That wouldn't work if DOUG was a subroutine.
Sometimes, for debugging in-use code I put in a line like 'IF @PORT =
(my current port) THEN DEBUG' - remembering to take it out afterwards!
Often this is enough to help track down issues without affecting other
users...
Edward
-Original Message--
Why not just catalog the original in EURO.BP for the end users, and do a
RUN DOUG.BP DOUG when testing your changes.
Dan Goble
RATEX Business Solutions, Inc.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of doug chanco
Sent: Thursday, May 22, 2008 9:21 AM
The best would be to have a development account to separate the code.
Without that option, the easiest would be to rename the program in DOUG.BP
to something a bit different (I.e. DOUG.DEV). compile and catalog the
original DOUG in EURO.BP and DOUG.DEV in DOUG.BP. Users could run the
original
I have been informed that I was a little off on my time to the borders of
Missouri. We are actually about 3 hours to any border of the state. I'm glad
that I've gotten some responses, keep them coming in.
Jerry Banker
Senior Programmer Analyst
IBM Certified Solutions Expert
---
u2-users m
I am out of the office until 27/05/2008.
Please contact Kenton Turner on 07801 684291 in my absence.
Note: This is an automated response to your message U2 Users Digest V1
#2220 sent on 22/5/08 9:00:08.
This is the only notification you will receive while this person is away.
---
u2-users ma
12 matches
Mail list logo
