our developers have asked us to create a clone database (a collection of
10
segments) within the same development CV as the original (this will
never
be done in prod).
the caveat - they want to be able to execute all programs against either
database with no program changes. For batch - no problem - sysidms to
the
rescue - but CICS is a problem
from a CICS menu - the app jumps into the CV and executes a ADS/A user
menu. We can determine from what CICS the jump came from - we could move
something to DB-NAME in the premap and response of the user menu dialog
-
however - since the user menu does no DML - no bind takes place and no
dbname is set
does an execute next function extend a run unit - or at least preserve
the
dbname (of it did - i would put SOME dml in the user menu to force a
bind)?
is there any other way to preserve the dbname across sibling dialogs
within
an ADS/A structure? or is an exit the way to go?
any thoughts would be greatly appreciated
Chris Hoelscher
Senior IDMS & DB2 Database Administrator
Humana Inc
502-476-2538
choelscher@humana.com
The information transmitted is intended only for the person or entity to
which it is addressed and may contain CONFIDENTIAL material. If you
receive this material/information in error, please contact the sender
and delete or destroy the material/information.
The information transmitted is intended only for the person or entity to which it is addressed and may contain CONFIDENTIAL material. If you receive this material/information in error, please contact the sender and delete or destroy the material/information.
"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP
Normal
Normal
Re: a dilemma (my lack of ADS exposed again)
"There are a number of possibilities here - some of which have some
subtleties that you need to watch out for.
1) The DCUF solution works if you do the DCUF in a ""front-end"" mainline
dialog that then does a ""LEAVE ADS NEXT TASK 'task-code'"" - where the
task-code is the correct task code for the desired application. The
reason for this is that when ADSORUN1 fires up it picks up the current
DBNAME for the User Profile as it currently sits either after signon and
User Profile setting takes place, or as the result of user session
tailoring (for example using DCUF). Whichever way the DBNAME in the User
Attribute Block has been set - it is preserved in the ADS system
variable DB-NAME - so a DCUF once in the application is of little value.
2) Since your menu function does no DML and so no bind run unit /
currency save processing takes place - you can do a ""MOVE desired-dbname
TO DB-NAME."" ADS statement to set the ADS system variable DB-NAME that
will be used when you do eventually bind the first run unit in the
application thread.
3) If the Users who will be running against the particular physical
instance should only ever use that physical instance (that is for this
current period of development/testing they should only be using one copy
or another) then in the User Profile for these users you can code
""DBNAME = 'desired-dbname' OVERRIDE NO"" - this will force the online
users to only use the desired copy of the database - this would be my
preferred solution if it's the case that some users should only use one
instance and other users a 2nd (or 3rd, etc) instance of the database.
We have some Exit 14 code to enforce this restriction when SYSIDMS is
used to specify DBNAME=desired-dbname so that whether in batch or online
the users are effectively ""fenced"" into one physical instance of a
database or another.
HTH - cheers - Gary
Gary Cherlet
Justice Technology Services
Department of Justice, SA Government
Telephone +61 (0)8 8226 5199
Facsimile +61 (0)8 8226 5311
Mobile +61 (0)41 333 1613
MailTo:
cherlet.gary@saugov.sa.gov.au
This e-mail message and any attachments are qualified as follows:
Addressing: If you have received this e-mail in error, please advise by
reply e-mail to the sender. Please also destroy the original
transmission and its contents. Confidentiality: This e-mail may contain
confidential information which also may be legally privileged. Only the
intended recipient(s) may access, use, distribute or copy this e-mail.
Individual Views: Unless otherwise indicated, the views expressed are
those of the sender, not Justice Technology Services. Computer Viruses:
It is the recipient's responsibility to check the e-mail and any
attached files for viruses.