Frosty the Coder
Legendary Poster
List:
First, I'm an old (400/world) dog, trying to learn new (oneworld) tricks.
Should I occasionally grouse, please forgive me.
It's busy season, and machine time for package builds
has been declined.
To date, we've been able to circumvent package builds for
UBEs by making the changes on a fat client, and then doing
a checkout/erase checkout on the citrix servers getting the
specs to the thin clients.
My latest specs, when run locally work fine. I've checked
them into the server, we did our citrix procedure, but the specs
don't run as they should on either citrix or server.
I checked them back out to the fat client on which they were
mod'd, and they still run as I want locally. I checked them
back onto the server, run them from the server, and I still
get the old results.
Where would I look to see what's going on?
I remember, briefly being shown a .log for checkins.
What is the name of that log?
If the specs produce the old results on the server, why do they still
produce
the new results when run locally AFTER being checked out from that server?
TIA
Gene Piekarski, Jr.
Gene Piekarski, Jr
AS/400, B733, SP11.2, NT client
First, I'm an old (400/world) dog, trying to learn new (oneworld) tricks.
Should I occasionally grouse, please forgive me.
It's busy season, and machine time for package builds
has been declined.
To date, we've been able to circumvent package builds for
UBEs by making the changes on a fat client, and then doing
a checkout/erase checkout on the citrix servers getting the
specs to the thin clients.
My latest specs, when run locally work fine. I've checked
them into the server, we did our citrix procedure, but the specs
don't run as they should on either citrix or server.
I checked them back out to the fat client on which they were
mod'd, and they still run as I want locally. I checked them
back onto the server, run them from the server, and I still
get the old results.
Where would I look to see what's going on?
I remember, briefly being shown a .log for checkins.
What is the name of that log?
If the specs produce the old results on the server, why do they still
produce
the new results when run locally AFTER being checked out from that server?
TIA
Gene Piekarski, Jr.
Gene Piekarski, Jr
AS/400, B733, SP11.2, NT client