CMAX Technical Support

The data source for producing this report on the host system is the SYSTEM.CONTROL,nnn file (where 'nnn' = branch #). The file is updated daily by a 'FM' type URT produced by each store during the end-of-day process by program CS302.SYS. Specifically, this report uses the *LAST.UPDATE, *REGISTRATION, and DIAGNOSTICS items from this file.

Sample CM782 output:

NOTE: All registration related messages use the system date on the home office computer for determining expiration dates. Also, remember the data from the branch being used to produce the report is up to date as of the 'Last Update' date shown on the report for each branch.

Most of the above diagnostic messages should be self-explanatory, and as of now, all possible errors that will print are shown above. A brief explanation of each message, possible cause and possible solution follows:

STORE CLOSED, NO UPDATES WITHIN LAST 30 DAYS, DIAGNOSTICS/SYSTEM.CONTROL FILE DELETED ON HOST.

• The store master record on the host system contains a value in the 'date closed' field and no 'FM' URT for the SYSTEM.CONTROL item has been received within the last 30 days from the branch. In this case, the SYSTEM.CONTROL,nnn data file on the host system is deleted.
  
  
• This branch will not appear on any further diagnostics reports unless the date closed is removed from the store master.
  
  

THIS STORE HAS STOPPED REPORTING DIAGNOSTICS, POLLING OR VERSION ERROR.

• The store has transmitted at least one 'FM' URT on the SYSTEM.CONTROL file to the host and the corresponding data file was created in the host SYSTEM.CONTROL file; however, the host has not received an update 'FM' within the last 3 days. The date that the last 'FM' was received appears in the Last Update column.
  
  
• Possible cause is most likely a version error at the branch. The branch system was reloaded using outdated CheckMAX software, or an older version of the PAM item CS302, that does not execute the CS302.SYS program, was sent to the branch. The easiest way to determine this is to examine the URT file at the branch for the most recently closed out date. There should be a 'FM' type URT immediately following the 'STD' URT with the same TRAN.DATE. If this is not the case, you must send the PAM item CS302 (updated version), BP item CS302.SYS and MD item CS302.SYS to the store.
  
  
• Another possible cause is simply that the branch hasn't been polled in the last three days, or URT's from the branch have not yet been processed on the host. In this case, simply poll and catch up URT processing to remove the message. - It is also possible that the branch has been closed down and no one has entered a 'date closed' in the store master on the host. If this is the case, enter the date closed.

STORE HAS NEVER REPORTED DIAGNOSTICS, POLLING OR VERSION ERROR

• The store has a 'date opened' value and no 'date closed' value in the host store master file; however, the host system has never received a 'FM' URT on the SYSTEM.CONTROL file from the store. If the store is not actually opened and operating yet, you can simply ignore this message. If the store is never going to open, the store master item needs to be deleted, or a 'date closed' needs to be entered.
  
  
• If the store is actually opened and operating, then the most likely cause of this message is a version error at the branch. The branch system was loaded using outdated CheckMAX software, or an older version of the PAM item CS302, that does not execute the CS302.SYS program, was sent to the branch. The easiest way to determine this is to examine the URT file at the branch for the most recently closed out date. There should be a 'FM' type URT immediately following the 'STD' URT with the same TRAN.DATE. If this is not the case, you must send the PAM item CS302 (updated version), BP item CS302.SYS and MD item CS302.SYS to the store.
  
  
• Another possible cause is simply that the branch hasn't been polled yet, or URT's from the branch have not yet been processed on the host. In this case, simply poll and catch up URT processing to remove the message.
  
  

ABS FRAMES DO NOT VERIFY, RESTORE ABS IMMEDIATELY!

• Just as it says. The ABS Frames must be reloaded by booting the remote system using the system disk #1. Don't forget to execute the one-step install in Laguna after reloading the ABS Frames!
  
  

9999 SYSTEM ERROR(S) WITHIN LAST 7 DAYS, POSSIBLE GFE'S OR HARDWARE FAILURE.

• This error is produced as a result of the CS302.SYS bp executing a query on the SYSTEM-ERRORS file for all items other than 'coldstart' (type C) errors that have occurred with the last 7 days. CS302.SYS uses the computer date, NOT the CheckMAX work date, for purposes of this query. This message is intended as a prompt to notify someone at the home office to dial-in and inspect the actual SYSTERM-ERRORS file in the SYSPROG account, check for group format errors, verify the system, etc.
  
  
• Possible error types include abnormal system aborts/halts, power fail signaled by UPS, hard disk errors, group format errors, etc. - NOTE: In our initial testing, we found that a high number of system errors in the message, tended to point to the 'power fail' boot option being enabled on systems that do not actually have the UPS (uninterrupted power supply) interface cable installed and are using a laser printer on the parallel port. To remedy this, either install a proper UPS interface cable, or reboot the system and disable the power fail boot option on the Pro4 boot screen by typing a signal 'P' before the usual 'X' to boot.
  
  

********** CHECKMAX REGISTRATION EXPIRES TODAY!! ***********

• The CheckMAX system has been prompting branch personnel for registration updates for 30 days! The 30 day period has now elapsed without registration. The system can still be registered, free of charge, by having the store personnel call CMAX before the end of the day.
  
  

********** CHECKMAX REGISTRATION EXPIRED ON 8/30/99!! ***********

• The prompt for CheckMAX registration has been ignored by branch personnel for over 30 days. If the branch personnel did not call CMAX before the end of day on 8/30/99 and the store personnel cannot log into CheckMAX, CMAX support will have to be called to update the registration information manually.
  
  

CHECKMAX REGISTRATION EXPIRES IN 10 DAYS

• The CheckMAX registration will expire in 10 days. The system can still be registered, free of charge, by having the store personnel call CMAX before the expiration date is reached.
  
  

NO CHECKMAX REGISTRATION ITEM FOUND ON HOST FOR THIS LOCATION.

• The Remote Branch appears to be reporting diagnostic ('FM' URT) information, even though the SYSTEM.CONTROL,nnn file on the host system does not contain an *REGISTRATION item.
  
  
• Possible causes include file damage on either the host or remote system. In either case, CMAX support involvement is most likely necessary in order to track down and correct the problem.
  
  

RUNNING LOW ON FREE DISK SPACE, nn% OF DRIVE CAPACITY REMAINING.

• The program CS302.SYS will begin including available disk space notices in the 'FM' URT at the end-of-day, whenever the amount of free disk space on the remote system falls below 20% of the drives capacity. There are several possible solutions for eliminating this message: 1) Run data purges found on the CheckMAX System Maintenance Menu, 2) search for and remove unused 'temp' files, lists, etc. that may be taking up space on the system, 3) perform a filesave/fileload to reorganize and reclaim lost frames, 4) install a larger hard disk, or 5) most likely, a combination of all of the above.
  
  

PRINT SPOOLER CONTAINS AN UNUSUALLY HIGH NUMBER OF ENTRIES…SYSTEM WILL HANG UPON REACHING CAPACITY.

• The program CS302.SYS will begin including print spooler notices in the 'FM' URT at the end-of-day, whenever the number of spooler entries (i.e. print jobs) exceeds approximately 300. The spooler capacity on a Mentor PRO 4 system is 599, and varies on other Pick platforms. In any case, 300 is an exceptionally high number of jobs to be in the spooler and in addition to posing a risk of hanging the system, can significantly degrade system performance.
  
  
• Possible causes include the use of invalid printer queues in CheckMAX setup, the use of the "CP nn" command within CheckMAX to redirect printed output to an invalid queue, or a printer not functioning properly in order to allow the spooler to de-spool the print job (cable is off the printer, printer is off-line, etc.).
  
  
• In the case of invalid print queues, these jobs must be deleted through the SP.MGR screen in CheckMAX or the corresponding TCL commands. - In the case of a printer/cable problem, correct the problem should cause the restart de-spooling and the printed jobs will be removed from the spooler upon completion.
  
  

UNKNOWN ERROR TYPE "xxx" REPORTED BY STORE.

• The program that produces this report (CM782) encountered a type of message (where the xxx in the report line would contain the actual message type) in the SYSTEM.CONTROL,nnn DIAGNOSTICS item that it does not recognize.
  
  
• Possible causes include data transmission or processing error between the store to host system, or a version error on the host side CM782 program. In either case, CMAX support personnel should be involved in determining the source of this problem.