Mecki,
When I have questionable catalogs stuff, I always type:
DELETE.CATALOG xxxxxx
several times until it states that there is nothing there. That ensures that
if it was cataloged locally AND globally, there is no cataloging left for that
program (at least in that account). I then re-catalog the way I know it should
be (always directly unless it is the parent trigger program).
I appreciate the value of audits. I can't tell you how many times a person
used to show up angry that someone messed up THEIR DATA, and with the audit
trail, I am able to prove that THEY DID IT THEMSELVES!
Another thing to try if you have not already done so is to re-compile and
re-catalog all programs. While this is a pain to do, it does ensure that
you're code is taking advantage of the current compiler and that programs are
cataloged correctly.
All in all, it sounds like you are on the right path.
Let me know if you still have trouble.
John Israel
Senior Programmer/Analyst
Dayton Superior Corporation
1125 Byers Road
Miamisburg, OH 45342
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of Mecki Foerthmann
Sent: Tuesday, February 22, 2011 12:27 PM
To: U2 Users List
Subject: Re: [U2] Catalog copy error
Thanks John,
SYSS4915.2 is part of the Avante File Auditing module (I think it was
actually retro-fitted onto our 5.2 system and the different processes
can only be invoked using the slash-processor).
In this module you can set files and attributes therein up to record any
changes with time and date of the change, what was changed and who did it.
This is sometimes helpful if nobody owns up to having changed the status
of a Work Order Operation when it shouldn't have been for instance.
There is even a process SYS4913 that generates a report on those audited
files.
Not very nice and half of the options don't work, but better than nothing.
But maybe this is just an Epicor UK thing?
I managed to delete the triggers on SYSCON and now at least I get the
Avante menu up and it seems to prove that at least SB+ 5.2 is still
working and that it was actually a trigger causing my initial problem.
It doesn't solve my cataloging problem, though.
I actually don't mind that trigger subroutines need to be globally
cataloged.
Triggers actually fall over if you catalog the subroutine locally.
The only thing that puts me off a bit is that you have to own the file
if you want to create or delete triggers.
When installing UD 7.2 we used /usr/igi/ud72 as the UDTHOME directory,
while on the old system this was /usr/igi/ud52.
Of course there are file pointers in the VOC that were still pointing to
/usr/igi/ud52/... like CTLGTB for instance.
I changed CTLGTB and D_CTLGTB to the new location (CTLG is a local file
anyway and the others are language files etc.)
I also changed the group and gave all files 777 permissions and changed
the group from root to infoflo, but that COPY CATALOG FILE ERROR still
comes up when I try to catalog any programs.
Maybe we should just start all over again and call the UDTHOME directory
exactly the same as on the old system.
Setting up logical file pointers in Solaris may have screwed things up.
On 22/02/2011 14:07, Israel, John R. wrote:
> We are also using Avanté, but we do not have a program called SYSS4915.2.
> Nor do we have SYSS4915.1.
>
> I don't believe that TRUE UniData triggers are part of Avanté. We use them,
> but they have all been written in house. Epicor uses things that they CALL
> triggers, but they are not true triggers in the sense of what UniData calls
> them.
>
> Based on those statements, I am not sure where to point you.
>
> True UniData triggers must be globally cataloged. This can cause headaches
> if you have a LIVE and TEST (and possibly other) realms on your box. To get
> around this, a popular naming convention for triggers is to globally catalog
> the .1 program, but all it really does is call the .2 subroutine which is
> locally cataloged.
>
> I hope some of this points you towards something userful.
>
>
> John Israel
> Senior Programmer/Analyst
> Dayton Superior Corporation
> 1125 Byers Road
> Miamisburg, OH 45342
>
>
> -----Original Message-----
> From: [email protected]
> [mailto:[email protected]] On Behalf Of Mecki Foerthmann
> Sent: Tuesday, February 22, 2011 8:56 AM
> To: U2 Users List
> Subject: [U2] Catalog copy error
>
> Hi
>
> I finally got the chance to try to upgrade of the company's old
> UD/Solaris 5.2 system to 7.2.
> I got a separate machine with a later version of Solaris to play with.
> We installed UD7.2.5 and copied all the Avante directories from the old
> system to the new.
> Initially everything went quite smoothly, but when I try to log on to
> Avante 9.2 I get an error before the menu comes up.
> *SYSS4915.2 is not cataloged
> DELETE Error
> Fatal error
>
> And the system drops to TCL.
> The same happens if I type MM to get back into the menu structure.
> BTW SYSS4915.2 is a standard Avante DELETE trigger subroutine.
>
> When I try to catalog the program (or any other one) I get a COPY
> CATALOG ERROR message.
> I checked the permissions of the CTLGTB file and they ate rw-rw-rw just
> like the old system.
>
> Any suggestions?
>
> Thanks
>
> Mecki
> _______________________________________________
> U2-Users mailing list
> [email protected]
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>
> _______________________________________________
> U2-Users mailing list
> [email protected]
> http://listserver.u2ug.org/mailman/listinfo/u2-users
>
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
_______________________________________________
U2-Users mailing list
[email protected]
http://listserver.u2ug.org/mailman/listinfo/u2-users
