What I have been doing is creating a new revision to PART.MGR.R101.
Called PART.MGR.R102
Thus when PART.MGR.R102 has been tested in the SandBox, VOC in our live system
is updated from ...101 to ...102 to something like...
>ED VOC PM
1: PA
2: RUN B.INV PART.MGR.R102
--Bill
-----Original Message-----
From: [email protected]
[mailto:[email protected]] On Behalf Of George Gallen
Sent: Wednesday, November 03, 2010 2:56 PM
To: U2 Users List
Subject: Re: [U2] Cataloging Programs
the biggest I can think of, is that it allows you to compile a programs changes
and test them, without interferring with production (if they are running the
cataloged program), once it's ok - then recatalog to put into the production
usage.
> -----Original Message-----
> From: [email protected] [mailto:u2-users-
> [email protected]] On Behalf Of Bill Brutzman
> Sent: Wednesday, November 03, 2010 2:53 PM
> To: U2 Users List
> Subject: [U2] Cataloging Programs
>
> Although I have been globally cataloging subs for some time, is there
> any point in cataloging standard application programs?
>
> Of course, end-users are able to launch the compiled application
> programs via VOC.
>
> Suggestions would be appreciated.
>
> --Bill
>
>
> _______________________________________________
> 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