COVERED_ADD command can be issued to "cover" an area (or an entire database) without recycling the MUF region. This command can be issued from the system console, running a DBUTLTY COMM function or executing an SQL query (e.g. via DBSQLPR).
An example for this command is:
This command will cover PMF area of DBID 001 (see COVERED_ADD description in the CA Datacom/DB Database and System Administration Guide for details).
However the code related to this command requires that at least one MRDF area is defined at MUF startup, i.e. there is at least one valid VIRTUAL or COVERED card in MUF SYSIN. We expected that every client already had a VIRTUAL CBS index and/or TTM and so this was a logical decision.
If no MRDF area already exists, the command gets the following error messages:
F jobname,COVERED_ADD 001,IXX,105,F,0
DB01311I - COVERED_ADD 001,IXX,105,F,0
DB01335I - CONSOLE SCHEDULED - COVERED_ADD 001,IXX,105,F,0
DB00605E - CONSOLE BAD SYNTAX - COVERED_ADD 001,IXX,105,F,0
COMM OPTION=CONSOLE,OPTION2='COVERED_ADD 001,IXX,105,F,0'
DB13001E - UNEXPECTED RETURN CODE 94 (129) INVALID DST CONTEXT
DB10045E - ABNORMAL TERMINATION DUE TO ERROR(S)
SQL Query (DBSQLPR):
INSERT INTO SYSADM.SQL_CONSOLE (MUF_NAME, CONSOLE_COMMAND ) VALUES ('mufname', 'COVERED_ADD 001,PMF,105,F,0');
SQLCODE = -117, SQLSTATE=S9481, DB RETURN CODE = 94(129)
MESSAGE = RAAT/CBS ERROR: CMD=ADDIT TBL=SQX DBID=00998 KEY= RC=94 (129)
The solution is to be sure that you have at least one COVERED or VIRTUAL entry in the MUF Startup Options before using this command.