I know that the designer saves and compiles the DDS and that I can compile that same DDS using the CRTDSPF command either manually or through my change management system.
My question - are there any recommendations or requirements for the CRTDSPF parameters? What are the default parameters that the designer uses?
Thanks!
Jim
Compiling DDS through Change Management System
-
- New User
- Posts: 13
- Joined: Sun Feb 05, 2012 5:44 pm
- First Name: Jim
- Last Name: Rohde
- Company Name: TMW Systems
- Phone: 440-721-2931
- Address 1: 6350 Quadrangle Dr
- Address 2: Suite 300
- City: Chapel Hill
- State / Province: North Carolina
- Zip / Postal Code: 27517
- Country: United States
- Contact:
- David
- Profound Logic Staff Member
- Posts: 690
- Joined: Fri Jan 04, 2008 12:11 pm
- First Name: David
- Last Name: Russo
- Company Name: Profound Logic Software
- Contact:
Re: Compiling DDS through Change Management System
Profound UI uses system default parameters, and not many of them will come into play, anyhow.
For example, some typical options that people use on a green screen:
* PUI always behaves as if RSTDSP(*YES), SHARE(*NO), and WAITRCD(*NOMAX) are in effect, regardless of the actual compile option used.
* MAXDEV(1) is the only value allowed for RPG Open Access.
For example, some typical options that people use on a green screen:
* PUI always behaves as if RSTDSP(*YES), SHARE(*NO), and WAITRCD(*NOMAX) are in effect, regardless of the actual compile option used.
* MAXDEV(1) is the only value allowed for RPG Open Access.
Who is online
Users browsing this forum: No registered users and 5 guests