Customer Support for F1 MANAGER

Problem Reports

Affected release level: 3.20

Problem Description:

A customer reported that they are unable to run a purge of the F1 Manager History file from the utilities menu. Any attempt to run the procedure results in an error message that there is something wrong with the purge dates entered.

We have identified four statements in the OCL procedure named F1M008 that need to be removed so that this can work. All changes involve "commenting out" the specific OCL lines in question. These OCL statements are two pairs located next to each other. The first pair looks like this:

// IFF ?L'205,2'?>83 GOTO DATERRS       * Edit year
// IFF ?L'211,2'?>83 GOTO DATERRE

It should be changed to look like this:

** IFF ?L'205,2'?>83 GOTO DATERRS       * Edit year
** IFF ?L'211,2'?>83 GOTO DATERRE

The second pair of statements is four statements later in the OCL procedure. Before the change, they look like this:

// IFF ?L'194,6'?>?L'125,6'? GOTO ENDRS       * Logical edit
// IF ?L'188,6'?>?L'48,6'? GOTO STARTERR

It should be changed to look like this:

** IFF ?L'194,6'?>?L'125,6'? GOTO ENDRS       * Logical edit
** IF ?L'188,6'?>?L'48,6'? GOTO STARTERR

After this change has been made, the purge will work correctly. You will be restricted, however, to only running purges that DO NOT cross the January 1, 2000 boundary.

Affected release level: 3.20

Problem Description:

Customer is using F1 Manager on a new AS/400 running under an SSP Guest machine. They would like to have a new original install tape but their new system does not support the older QIC-60 tape density normally supplied to customers ordering F1 Manager on tape.

We have now developed a method for distributing F1 Manager on QIC-120 tape format. Contact us if you would like to receive your copy of F1 Manager in this format.

Affected release level: 3.20

Problem Description:

Customer who has moved F1 Manager onto their new Advanced System/36 Model 9402-236 questioned about saving "Licensed Internal Code" as described in Chapter 10 of their new manual titled "Operating Your Computer-9402 Model 236".

After examining the manual, we conclude that you must perform the recommended step of saving the Licensed Internal Code to have a complete and safe backup of your system. There is a 14 step procedure outlined in the manual on pages 10-2 through 10-6 that you should follow. Also, as a reminder, F1 Manager DOES NOT backup the SSP as already stated in our user guide. A procedure outlined on pages 10-6 and 10-7 of this same manual takes care of this task as well.

Affected release level: 3.20

Problem Description:

A customer was calling the Master Save (F1MSAVE1) from within their own OCL procedure. The customer specified that NO messages be issued to the console (parm 5='N') but the backup issued messages anyway.

Problem traced to an incorrect OCL specification in our procedure. To fix the problem, you must edit the F1MSAVE1 procedure in our library named F1MLIBR. Locate the statement that reads as follows:

// TAG RUNME

The following statement must be changed to read as follows:

// TAG F1MSAV1Q ?1?,?2?,?3?,?4?,?5?

This will resolve the problem.

Affected release level: 3.20

Problem Description:

Customer using Application Group save found that some files in the group were not saved.

Problem traced to the fact that the group defined by the customer was very large, thereby exceeding an internal table in the program. No more that 998 files, libraries or folders can be included in a group. The solution was for the customer to break up the group into two smaller groups. We also expanded the internal table in the program to accommodate a table size of 1200. This modified version of the program is now available.

Rich Loeber, President

Contact Information

Phone: (914) 241-7233 Fax: (914) 241-9140

E-mail your questions or suggestions: Support@Kisco.com

Return to Customer Support Page