It has been a long time since I've done this also, but I recall something 
about the catalog having to be re-indexed after editing it.

Bob Comeau
Sr. Systems Programmer  Analyst
Tandus Canada / Crossley Carpet Mills Ltd.
(902)895-5491 ext 139



Matthew Perdue <[log in to unmask]> 
Sent by: HP-3000 Systems Discussion <[log in to unmask]>
06/05/07 06:11 PM
Please respond to
Matthew Perdue <[log in to unmask]>


To
[log in to unmask]
cc

Subject
Re: MPEX errors...was... Adager errors






Yes, I was referring to CATALOG.PUB.SYS. If you do a LISTF ,9 on that file
you'll see the only process accessing it is #P1 as MANAGER.SYS 
(PROGEN.PUB.SYS)
- at least on my system. Easy to check, and that's why it has the "*" when 
you
do a LISTF,2. There are files "attached" by MPE that HP wants to either 
have
open for exclusive read (such as CATALOG.PUB.SYS) or exclusive write (log
files). There are others but HP probably would prefer those remain 
undiscovered
(too late in my case, I get curious but not dangerous).

Any changes to the file can cause problems if you're not careful. I too in 
the
past changed some of the messages, mainly to add inverse video and blink 
for
certain messages that would appear on the console. Many sites change the
default error messages related to log on errors to hamper hackers. I'll 
admit
it's been so long since I've changed that file I'd have to look it up to 
be
sure I did it correctly.

Quoting "Newton, Ernie" <[log in to unmask]>:

> Thanks Matthew, these are indeed MPEX errors.
>
> We run DBADGALT from within MPEX, that's were the confusion, (mine),
> came from.
>
> You refer to a system message file.  Are you referring to
> CATALOG.PUB.SYS?
>
> I WAS messing with CATALOG.PUB.SYS a couple of weeks ago, could that
> have
> corrupted the file?
>
> I know that you can modify messages in that file.  I use to do it for a
> fortune 500
> company I worked for years ago.  They didn't like the logon errors, like
> "Non-existent account",
> so I changed those messages to simply "Invalid" to make it harder to
> hack in.
>
> I also noticed that no application is accessing the catalog file and it
> usually has an asterisk when doing a LISTF ,2.
>
> Thanks,
>
> Ernie
>
> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> Behalf Of Matthew Perdue
> Sent: Tuesday, June 05, 2007 11:57 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Adager errors
>
> To me it doesn't look like an Adager error at all, but one you're
> getting while running MPEX (from the great folks at Vesoft, not from the
> great folks at Adager).
>
> It appears your system message file may have been corrupted or in some
> instances where MPEX has been "hooked" into various system (HP) and
> third party utilities MPEX will in the background redirect commands and
> file equations various places and a message file in a third party tool
> may have been corrupted.
>
> At a site that shall remain nameless, everyone was frustrated that when
> they issued commands from a menu interface the commands were not
> operating on the expected databases, but the commands would work
> correctly from within certain HP utilities but not others (such as
> EDITOR.PUB.SYS and QUERYNM.PUB.SYS).
> Research determined editor and querynm had been "hooked" and the
> commands were redirected, including file equations. Restoring the
> original, good from HP programs to the system and replacing the "hooked"
> application programs solved the problem.
>
> Bottom line: check if 1) the problem is related to MPEX and not Adager
> and 2) check if some of your utilities and programs, including Adager
> have been "hooked" by the MPEX process.
>
> Quoting "Newton, Ernie" <[log in to unmask]>:
>
> > Greetings,
> >
> > We have jobs that run nightly that check our database capacities 
and=20
> > they are getting weird errors.
> >
> > These two happened last night.
> >
> > The jobs finish okay, but I'm just curious about these things.
> >
> > What is the program trying to tell me?
> >
> > *************************
> > % !MPEXTELLBACKCMD !MPEXTELLPREFIX DONE!
> > Error: Can't get message in set 2, message 1619, p0=3D3D!, p1=3D3D
> >
> > %SHOWVAR MPEXNUMSUCCEEDED
> > MPEXNUMSUCCEEDED =3D3D 0
> > %IF MPEXNUMSUCCEEDED =3D3D 0
> > Error: Can't get message in set 7, message 40, p0=3D3D, p1=3D3D
> >
> > *************************
> >
> > Is the message number referencing the CATALOG.PUB.SYS file?
> >
> > Thanks,
> >
> > Ernie

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *


* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *