|
Do a CRTDUPOBJ on CRTLF, twice. The first time store it into a BPCS library. The second time store it into a user library that will be in the library list for the other applications but not BPCS. Rename the original CRTLF to XCRTLF. Do a CHGCMDDFT on one of the copied commands to get the SHARE changed. When you upgrade operating systems do a WRKCMD X* to find your renamed commands, or as other users pointed out, just type in x* and hit enter. There will be some extreme opinions about this. One camp will say IBM is the supreme being and you shouldn't mess with anything in their libraries. Others will say that the 400 is not an open system because IBM doesn't provide source. Pros and cons both ways. One concern, what happens when you install that 'New' package that doesn't use either user library? Heck, how often do you do that? Go for the rule, let the exceptions prove the rule. Cost/benefit, risk analysis, blah, blah, blah..... dah6696@Goulds1.com on 08/28/98 01:02:41 AM Please respond to MIDRANGE-L@midrange.com@Internet To: midrange-l@midrange.com@Internet cc: Subject: CRTLF SHARE parm management We have for years had the default value on the CRTLF command parm SHARE changed to *YES. We are now importing another divisions BPICS application and MUST have this value back to the IBM original default to *NO. What I'd like to do is test the users group profile and based on that set the parm to the appropriate value. ex: &GRPPRF = 'SSA' then CRTLF SHARE(*NO) else SHARE(*YES). Does anyone have a quick solution? I've looked of help in the API manual with no luck. Perhaps a validity checker wedge? --- Douglas Hart - Sr. Consulting Technical Analyst ITT Fluid Technology / Goulds Pumps 240 Fall Street Seneca Falls, New York 13148 (315)568-7568 Voice (315)568-7129 FAX mailto:dah6696@goulds1.com +--- | 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: david@midrange.com +--- +--- | 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: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.