When reporting a fault, please give us as much additional information as possible. As a guide, this is the information we would typically need:

• Product name and codefile version
• Level of MAGUS library
• Problem description
• Diagnostic information such as log trace, program dumps, screen dumps,

The ODT WM command or ?WM from CANDE will give you the MCP version. To obtain the version of the MAGUS library or a Metalogic application, please use the CANDE LFIL command or a PD from the ODT, MARC or Supervisor window:

LFIL *METALOGIC/SUPERVISOR
*METALOGIC : DIRECTORY
. SUPERVISOR : BOUNDCODE RELEASEID="480.22"

PD *METALOGIC/MAGUS
FILE *METALOGIC/MAGUS ON DISK (NEWPCODE) & (DIRECTORY) IN USE
CREATION DATE= Friday, February 15, 2002 AT 16:31:06 GMT
LASTACCESS DATE= Friday, March 15, 2002 AT 09:03:47 GMT
ALTER DATE= Friday, February 15, 2002 AT 16:31:06 GMT
ATTMODIFY DATE= Wednesday, March 6, 2002 AT 11:30:49 GMT
BACKUP DATE= Friday, February 15, 2002 AT 16:31:06 GMT
COPYDEST DATE= Wednesday, March 6, 2002 AT 11:30:38 GMT
COPYSOURCE DATE= Friday, February 15, 2002 AT 16:31:06 GMT
EXECUTE DATE= Friday, March 15, 2002 AT 09:03:47 GMT
READ DATE= Tuesday, February 26, 2002 AT 12:40:44 GMT
TOTAL SECTORS: 1,314 (504 PER AREA, CRUNCHED)
SECURITY = OWNER *:RWX, GROUP <none>:RWX, OTHER:RWX
(PUBLIC - USAGE: READ/WRITE)
RELEASEID: 480.08 
PRODUCT: METALOGIC 47.244
FAMILY SERIAL NUMBER: 000505

For Supervisor-related products, you can use the TT WS and TT TP VER commands to get version information about Supervisor, OPAL and the TRIM subsystem. The WHAT command in Flex Inquiry will give you version info about Flex itself and the METALOGIC/FLEX/LIBRARY codefile.

The most effective and fastest way to get diagnostic information to us is by email. If you still have the original files on your A-Series, you can use the Unisys WFL WRAP command to prepare a container that can be used to move data to a PC for forwarding.

The syntax for the WRAP command is:

	WFL WRAP <file list> INTO <container>

For example, to send a file which might be a taskfile caused by a program fault:

	WFL WRAP *BD/00001234/000TASKFILE INTO META/DUMPINFO

Please ignore any warnings you might get that the container can only be read by Unisys. The file META/DUMPINFO can be FTP-ed using BINARY transfer (not ASCII or we will be unable to read the contents) to any suitable PC. If the container is very large (greater than 0.5 MB) then we would strongly recommend that you compress the file using utilities such as WINZIP or ZIPMAGIC.

Alternatively, if Unisys NX/SERVICES is installed, you can drag'n'drop the container from a MCP share to the PC using Windows networking.

Please email the contents to us at support@metalogic.eu.com.

If you are upgrading your MCP level, we recommend that you check your current Metalogic software levels against those shown in our MCP compatibility matrix.

You may need an upgrade to a newer version of our software. If so, you may require a new release and we strongly advise that you upgrade your Metalogic software before migrating to the new MCP level.

Many of our customers run disaster contingency tests and would like to run our software during those tests. Often, the machines used for such exercises will NOT necessarily be the same system model and have the same serial number as the normal production machine(s).

As Metalogic software licence keys are constructed from machine style, system serial number as well as the version of the MAGUS library, attempting to run our software will inevitably fail unless you have previously arranged for temporary keys for the disaster machine.

If you are intending such tests, we will be happy to supply you with temporary keys for the duration of the exercise. Please contact shipping@metalogic.eu.com for more details.