The RAPID Products [ COMMUNICATOR 3000 XL, XL Release 1.1 (Core Software Release A.10.00) ] MPE/iX Communicators
COMMUNICATOR 3000 XL, XL Release 1.1 (Core Software Release A.10.00)
The RAPID Products
by Perry Mizota, Commercial Systems Division
As briefly described in the Communicator article, the internal interface
between Transact and called Inform and Report has been changed from a
procedure call to a created process.
CUSTOMER IMPLICATION CHECKLIST
The change made to the interface between Transact and called Report or
Inform could affect the execution of your existing base of Transact
applications. If you use Transact to access Report or Inform, please
review the following checklist to determine if your applications are
affected by this change, and, if they are, the appropriate corrective
action to take.
1. Do any of your Transact applications invoke Report or Inform via
the CALL verb?
If no, you are not affected by this change. Disregard the rest of
the checklist.
If yes, continue.
2. Are any of the data bases, MPE, or KSAM files defined in the
SYSTEM statement of the Transact programs, which call Report or
Inform, accessed by those called Report or Inform definitions?
If no, you are not affected by this change. Disregard the rest of
the checklist.
If yes, continue.
3. Are any of the data bases, MPE, or KSAM files accessed by both the
Transact program and the called Report or Inform accessed in an
exclusive manner (i.e., TurboIMAGE data base open modes 3 or 7)?
If yes, alter the data base open modes used by Transact to a
non-exclusive open mode compatible with the open modes used by
Inform and Report (default mode 5). Exclusively opened files will
also need to be opened for shared access.
4. Are any of the data bases accessed by both the Transact program
and the called Report or Inform definitions opened with modes
incompatible with the default open modes used by Report or Inform
(mode 5)?
If yes, alter the open modes used by Transact to modes compatible
with the default open mode used by Report or Inform (mode 5), or
alter the open modes used by Report to modes compatible with
Transact.
5. Are any of the data bases accessed by both the Transact program
and the called Report or Inform locked at the time the call to
Report or Inform takes place? This could either be a result of a
LOGTRAN(BEGIN)...,LOCK statement, or the PERFORM= option on a data
base access verb which has the LOCK option set.
If yes, make sure the data base lock is released prior to the call
to Report or Inform.
6. Do you have stream files which run Transact programs which call
Inform or Report?
If yes, make sure the stream files correctly answer prompts for
passwords and lockwords issued by Report or Inform when they open
data bases or files.
7. Do you use RAPID as a run time processor for Transact or Report?
If yes, change all invocations of the RAPID processor with PARM=1
to TRANSACT, and all invocations of the RAPID processor with
PARM=2 to REPORT in all UDC files and stream jobs.
MPE/iX Communicators