You can convert a non-UES-enabled VM database to a UES-enabled one. Once you have done so, you can verify that UES support has been added to a VM database.
Note:
If you have installed a new maintenance level of Adabas, make sure
that the APSvrs libraries were available when you
refreshed the ADAECS module in the Adabas load library. If they were not, retry
the refresh again with the APSvrs libraries.
Otherwise problems might arise when you attempt to implement or use UES support
for a database.
To convert a non-UES-enabled VM database to a UES-enabled one,
complete the following steps:
Load the CMS nucleus extensions required for UES support to your VM database. Use the supplied sample NUCXUES EXEC to assist you.
Note:
The NUCXUES EXEC must be run every time the database is started,
so you may find it simpler to call NUCXUES from your ADANUC EXEC.
/* ++++++++++++++++++/ A D A B A S VERSION 8.1 /++++++++++++++++++ */ /* */ /* NUCXUES - */ /* This EXEC loads the CMS nucleus extensions required */ /* for Adabas UES support. */ /* */ /* */ /* This EXEC is a sample. It is not a part of the ADABAS */ /* product and is not considered to be supported by any */ /* maintenance contract agreements. */ /* */ /* */ 'EXEC DEFNUCX ADAECS' 'EXEC DEFNUCX ADACOX' 'EXEC DEFNUCX SAGSMP2' 'EXEC DEFNUCX SAGECS' 'EXEC DEFNUCX SAGOVO' 'EXEC DEFNUCX PCAYRINI' 'EXEC DEFNUCX PCAYTRDB' 'EXEC DEFNUCX PCAYTRDH' 'EXEC DEFNUCX PLEYCFN' 'EXEC DEFNUCX PLEYBSD' 'EXEC DEFNUCX FEE' 'EXEC DEFNUCX SOFTLE' return 0
Locate the following lines in the ADANUC EXEC for your VM database:
address command 'DATADEF DDPRINT,DSN=NUC' || dbid'.DDPRINT,MODE=A' address command 'DATADEF DDCARD,DSN=ADANUC.DDCARD,MODE=A'
Once you have located these lines, insert the following lines after them and modify the file modes, as necessary:
ADDRESS COMMAND 'DATADEF SYSPARM,DSN=SMARTS.CONFIG,MODE=A' ADDRESS COMMAND 'DATADEF CONFIG,DSN=CONFIG.RTS,MODE=A' ADDRESS COMMAND 'DATADEF STDOUT,DSN=STDOUT.DDPRINT,MODE=A' ADDRESS COMMAND 'DATADEF STDERR,DSN=STDERR.DDPRINT,MODE=A'
A sample ADANUC EXEC is provided to assist you.
Copy the following to a minidisk or SFS directory that is accessible by a database machine.
APSvrs.CMSTAPE
APSvrs.CMSL014
ADAvrs.CMSEC00
Refer to the Report of Tape Creation to accurately locate these files.
Edit the SMARTS.CONFIG file provided. Specify a SYSTEM_ID in SMARTS.CONFIG using a value such as the virtual machine name of the VM database. This value is used in messages.
Here is a sample SMARTS.CONFIG file:
* SMARTS PARAMETERS
*
CDI=('FILE,PAASFSIO') NATIVE CMS FILE I/O
SYSTEM_ID=yoursysname
PROCESS_HEAP_SIZE=0
ABEND_RECOVERY=NO
THREAD_ABEND_RECOVERY=NO
LOG=OPER
ASCII=NO
FLOATING_POINT=IEEE
* TRACING PARAMETERS
*SYSTEM_TRACE_LEVEL=5
*TRACE_SYSTEM_INCLUDE=ALL
*TRACE_GROUP_INCLUDE=ALL
Run ADADEF for the VM database, specifying MODIFY UES=YES.
Start the ITM, the VM database, and Entire Net-Work.
You can verify that UES support has been added to a VM database in one of the following ways:
When the database starts, it should issue the following message:
ADAN7C 00001 ENTIRE CONVERSION SERVICES INITIALIZED
On the Entire Net-Work machine, issue the DISPLAY TARGETS command. The display for the UES database should look like this:
NET0124I: Target 00001 (I-T) active on node PTGITM
The highlighted T in this display stands for Translator. If the display shows (I-N), Entire Net-Work does not recognize that the database is UES-enabled.
Examples of jobs with UES support provided with Adabas include the ADANUC EXEC and the NUCXUES EXEC.
