|
We have the binder language as the source for the the *SRVPGM object in ACMS. -Kevin -----Original Message----- From: CWilt@xxxxxxxxxxxx [mailto:CWilt@xxxxxxxxxxxx] Sent: Wednesday, September 22, 2004 11:00 AM To: rpg400-l@xxxxxxxxxxxx Subject: ACMS Users, what names do you use for SRVPGM, Prototype, and BND lang? Wanted to start using binder language along with some service programs. Normally, given service program MYSRVPGM created from source named MYSRVPGM, I'd have prototypes in a different file with the same member name. Seems like the binder language source member should also be the same name in yet another file, but ACMS doesn't allow two *SRCMBR objects to be defined with the same name. Wanted to see what others were doing to handle this. Thanks, Charles -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l. ##################################################################################### Attention: The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from any system and destroy any copies. Thank You. #####################################################################################
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.