Hi Mark - >>Specifying OPTION(*DUPPROC) on the CRTPGM or CRTSRVPGM command will cause >>the first found procedure to be used. The default is for a fatal error if >>there are duplicates. > > 1) I don't care for the default (and CHGCMDDFT is not an option here). > > 2) In what case would the default be *good*? To protect us from ourselves? There are arguments on both sides as to where *DUPPROC or *NODUPPROC should be the default. I have mixed feelings myself so I'm going to take the coward's way out and leave that issue alone! <G> I think that the use of OPTION with multiple values so that CHGCMDDFT can't be used just plain sux. Each of the possibilities should be broken out into a separate parameter so that each shop could set the defaults to its own standards. One possibility to consider is creating a PDM user options for CRTPGM and/or CRTSRVPGM with the options specified that you want, something like: CRTSRVPGM SRVPGM(&O/&N) MODULE(&N) TEXT(&X) ACTGRP(*CALLER) OPTION(*DUPPROC *DUPVAR) DETAIL(*BASIC) REPLACE(&R) Ken Southern Wine and Spirits of Nevada, Inc. Opinions expressed are my own and do not necessarily represent the views of my employer or anyone in their right mind. +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: email@example.com +---
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.