|
That is some nasty looking code. I will never criticize rpg again<g>. Steve Richter ---------- Original Message ---------------------------------- From: "R. Bruce Hoffman, Jr." <rbruceh@attglobal.net> Reply-To: midrange-l@midrange.com Date: Thu, 16 Aug 2001 19:19:05 -0400 > WORKING-STORAGE SECTION. > 01 data-value. > 05 returned-packed1 pic s9(3)v9(2) packed-decimal. > PROCEDURE DIVISION. > move 345.67 to returned-packed1. > > DISPLAY data-value UPON data-area > FOR "DECDATA" LIBRARY "QGPL". > > ACCEPT data-value FROM data-area > FOR "DECDATA" LIBRARY "QGPL". > >=========================================================== >R. Bruce Hoffman, Jr. > -- IBM Certified Specialist - AS/400 Administrator > -- IBM Certified Specialist - RPG IV Developer > >"America is the land that fought for freedom and then > began passing laws to get rid of it." > > - Alfred E. Neuman > >-----Original Message----- >From: Tim Truax <truax@telerama.com> >To: COBOL400-L List <cobol400-L@midrange.com> >Date: Thursday, August 16, 2001 4:57 PM >Subject: Change *DTAARA from within a COBOL pgm ? > > >I have a COBOL 400 program that uses a call to QCMDEXC to change a *DTAARA >(Data area). >Is there a less overhead utilizing manner in which to change a *DTAARA from >within a COBOL program than using the QCMDEXC? >Maybe some similar way to the way RPG400 does it by using the IN opcode then >the OUT opcode? >Thanks! >Tim Truax :-) > > >_______________________________________________ >This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list >To post a message email: MIDRANGE-L@midrange.com >To subscribe, unsubscribe, or change list options, >visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l >or email: MIDRANGE-L-request@midrange.com > >
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.