Update Package server builds

I am building a small update package (2 objects), so far PAKTOTAM has been
running for 10 hours on the AS400.

This isn't right is it?

Thanks
Lucy

AS400, 7333 sp16.1

Just a guess but something isn't right . Kill it and start over using Package Build History.

D. Hursh
Archer, Daniels, Midland
OW Xe, NT, SP16.1, Update 1

No, it is not. We are on the same configuration. That sounds more like a full package build time. Maybe something got locked somewhere. gm.




I am building a small update package (2 objects), so far PAKTOTAM has been
running for 10 hours on the AS400.

This isn't right is it?

Thanks
Lucy

AS400, 7333 sp16.1




--------------------------


AS400 V4R5 Coexist CO-NT Xe SP16.1
Websphere 3.5.4 on AS400 JAS SP16.1

Nope - I would look at the build log and see what spec file it is hung on. I
have had a situation a couple of times where the process gets hung trying
to update the parent because the parent package specs got blown. I just copy
in the specs from one of my current Citrix clients and resubmit the build to
fix it.

Mark Siebenschuh




Mark Siebenschuh
HP9000/Oracle 8.0.5/JDE XE/Lots of Citrix

our avg for an update pkg (did 4 this week) is about 5 mins.



Jeremey Garcia
Xe SP14 ES - AS/400 CO - AS/400 Deploy - NT Citrix