Walt Farrell wrote:

>Any random application? Really?
>So, how does the issuer of a CICS transaction allocate the DD to affect how 
>the API call operates? Or the issuer of an IMS transaction? Or the issuer of 
>an SQL request that invokes a DB2 stored procedure?

 

And John McKown wrote:

>Oh, and to extend what Walt was saying; how does the API deal with
>multiple CICS transactions which invoke the API but want _different_
>effects from your API. Given your example, one needs the the DD DUMMY to
>enable something but another needs that there not be any such DD so that it
>is disabled. Or worse, different users of the same transaction / program
>want opposite processing from the API​ so the DD must both be there and not
>be there at the same time. I will bet that the simple answer is "we don't
>support use of our API under CICS." Why document not the same restriction
>about a program run from the UNIX shell? If you say that you have users
>which demand that some program be run via UNIX, then you have a customer
>demand which you should look into addressing. If you are saying that you
>don't want "dual pathing", that is checking for both an environment
>variable and a DD existing / not existing. It is easy to run an LE program
>in batch and set an environment variable via CEEOPTS instead of using a DD.
>Of course, this is an incompatible change.

 

Of course we support CICS. A CICS transaction generally isn’t going to switch 
it on-the-fly, but if it really must (we have a test transaction that allows 
this, for example) the switch *can* also be baked into the request. Normally in 
CICS it gets set globally for the region (by defining a dummy program—don’t 
need to add a DD). Similar options exist for IMS or DB2 stored procedures.

 

The reason for switching it for a batch job is more to allow the same code to 
run in test and prod, switching between cryptographic domains. So in most 
cases, it’s an administrative decision, not a user decision. Hence the desire 
to externalize it, but it’s not at the “oh, it’s Thursday, let’s do it this 
way” kind of thing; more “In this region, set it thus; for these batch jobs, 
set it that way…”.

 

Making more sense?


----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to