Hi All

I've got another site in the process of migrating from novell to windows 2000 something servers. The application had a check for the novell tsr thing coded into the start up programs for the application and two user environments. I need to be able to AREV SYSPROG to modify the user environments. Somehow I managed to modify the Application environment but now I can't do the user environments because I can't get into SYSPROG anymore.

AREV SYSPROG

results in the error

"the default macroset thismacro cannot be found"

I can get into the main application, and when I

LIST MACROS

thismacro is included.

There is a LOGON script in the VOC but as best I can tell - it doesn't do anything.

Does anyone know if I can start up SYSPROG and tell it not to run any start up options? Does anyone know where I should look for this default macroset thing?

The main application and user environments have stuff set into the startup and they don't complain about missing macroset thismacro. SYSPROG is supposed to have the start up options all blank. And when I start AREV SYSPROG on my development copy, I don't have this problem.

On my home copy, the MACROS table that is used by the main application is in a different place to the MACROS table used by SYSPROG. Only the one for the main application has the "thismacro".

I'd really like to stop sysprog from looking for the "thismacro" but I can't get into SYSPROG because it is looking… catch 22. Help please.

From the main application can you do a SETALIAS to the MACROS table used by SYSPROG and copy thismacro over?

That should work.

The SETALIAS command has the following syntax:

SETALIAS

In your case, I am assuming it would end up looking something like this:

SETALIAS REVBOOT SYSPROG, MACROS SYSPROG_MACROS

You have to include your sysprog password after the comma or it won't work.

Once you do this, you should be able to issue the following command:

COPY MACROS thismacro TO:(SYSPROG_MACROS

Hope that helps,

[email protected]

Greyhound Lines, Inc.

Hi all

I sorted it out, was going to try Matt's system but in the end I didn't need to. I do know the password to SYSPROG so this wasn't an issue.

First, for some reason SYSPROG's macros table was in a different directory to the main application, and in the SYSPROG environment settings - someone had put in the start up commands an attach and a thing to run the program that forced the LHIPXTSR to be loaded or logged us out.

I got around all of that by doing AREV LANPACK and F5 (TCL) and then RUNMENU STARTUP from there then Choose menu items "Options" + "Application

Then F2 for SYSPROG then remove all the bodgy stuff from the start up commands. F9 save, and F3 for more edit room.

It's funny when you hardly ever have to muck around in this bit, that you totally forget how to do it.

Once I'd forced it to stop running the chuck us all off program, the excelcare macro problem didn't actually log me out of sysprog, so I was able to create an empty record of the right name in the macros table - and that made that error go away. SYSPROG shouldn't have been running any of that stuff. And this problem was unique to one site - so somebody must have thought they were being helpful.

View this thread on the forum...