MAPICS 2 SYSLOK?

[Malak]

Hi, first of all some of you may remember that I'm the PC guy who got
stuck with the job of our IS400 guy when he passed away over a year
ago.

Things have been going well till I tried to replace the UPS batteries
while the system was running. I figured that as long as AC power was
good there should be no problem. Unfortunately, the $#*&^ UPS decided
to shut itself down while doing this and the system crashed.

Afterwards there were no perceptable issues except one particular PC
running Session can't update the customer master file.

Message says Building path for CUSALZPZ and error# SYS6277.

I'm thinking this is some sort of issue with either the M.SYSCTL or
M.SYSLOK files. Opinions on how to fix exactly? Also, I'm a little
unclear on how to restore the entire MAPICs from tape as he never
spelled this out before he passed. The files are in the "main"
directory i.e. QS36F so you can't really use restore library and not
sure that restoring all "files" in the QS36F directory really covers
it. I tried that and maybe I had a setting wrong because it mentioned
20 changes in security settings.

And yes I know we should get rid of old MAPICs. We have had quotes and
are just waiting for the $50-100K to be available to do it.

thanks much

Jim D.

[Malak]

Ok, it turns-out that when the system crashed, the user config file on
the PC
got corrupted. I tried reinstalling the Session software and that did
not do it.
It was only when I started the config file over again that it started
working.

[JTF]

Sounds like the workstation name is in a file to prevent the user from
doing such a thing as starting an update on a screen then closing the
screen.

You can try changing the client iseries connection name. Assuming you
are using Client Access, it is from the green screen session
COMMUNICATIONS>CONFIGURE and specify the workstation ID.

Or

Find MAPICS support and find out how to clear the user. I believe
there is a screen to clear this out.