Jim

I believe one can set a product library, too - is that right? Then the *LIBL strategy works very nicely.

Vern

-------------- Original message --------------
From: "Jim Franz" <franz400@xxxxxxxxxxxx>

When you create the menus (SDA)
change Prompt for paramaters to Y

Create menu objects . . . . . . . . . . Y
For choice Y=Yes:
Prompt for parameters . . . . . . . Y

On next screen - change the library parm for Display File and Message File
to *LIBL

Display file . . . . . . . . . . > DUMMY
Library . . . . . . . . . . . > *LIBL
Message file . . . . . . . . . . > DUMMY
Library . . . . . . . . . . . > *LIBL

or use CHGMNU cmd to change all existing menus before move to prod.
(create a clp to dspobjd to outfile and for each menu object execute
CHGMNU...)

Change Menu (CHGMNU

Type choices, press Enter.

Display file . . . . . . . . . . DUMMY
Library . . . . . . . . . . . *LIBL
Message file . . . . . . . . . . DUMMY
Library . . . . . . . . . . . *LIBL

Jim Franz


----- Original Message -----
From:
To:
Sent: Monday, September 08, 2008 10:58 AM
Subject: copying menu's from a test to a production library


RE: Find library of program to process a command, thanks all for your
help
with the previous issue.

New issue

We use the following scenario to promote test programs to production

put test library on top of library list, if no issues- run program to
copy
objects/source to appropriate production libraries, remove test library
from library list, next day rename test library to a save library

this works great except for menu's. the menu's need to be recompiled
after they are moved to the production libraries before the library they
were compiled in is renamed. anyone know a fix to this?

Jim Horn

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].