|
Michael,
With your help I am getting a little closer to getting this done.
Now I am getting this message: 'LABNO ' for parameter COPIES must be
numeric.
Error found on OVRPRTF command.
LABNO is defined in the display as 3s 0.
I tried the following 'eval' statement but got the same error.
nolbs 1 3s 0
eval nolbs = labno
I know and have used the 'Declare CL Variable (DCL)' in CL to pass numeric
values to OVRPRTF.
How is this done inside an RPG program?
Thanks,
Willie
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of
Michael_Schutte@xxxxxxxxxxxx
Sent: Wednesday, June 06, 2007 12:17 PM
To: RPG programming on the AS400 / iSeries
Subject: RE: Ovrsplf in rpgle program help
You missed my post... . It should be %Len(%Trim(cmd)) Because cmd
isn't varying, you are getting a length of the whole variable which isn't
necessarily the length of your command. Doing what I suggested will fix
that issue.
Michael Schutte
Admin Professional
Bob Evans Farms, Inc.
Visit us on the web! www.bobevans.com
(Embedded image moved to file: pic19895.gif)
What's the secret? Find out at your Bob Evans Restaurant on May 17!
rpg400-l-bounces@xxxxxxxxxxxx wrote on 06/06/2007 03:13:51 PM:
> This should not be that hard. But I am still learning the RPGLE.
> Using Debug, here is what is in these fields.
>
> C*
> C move *blanks @cmd 25
> @cmd has 25
blanks
> C eval len = %len(@cmd)
> Len = 25.
> 00000
> C EVAL @CMD = 'DLTOVR FILE(ADITALABRP)'
> @cmd =
> dltovr file(aditalabrp) '
> C CALL 'QCMDEXC'
> C PARM @CMD
> C PARM LEN 15 5
> C*
>
> Then get same error at call to QCMDEXC.
>
> Thanks,
> Willie...
>
> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Michael Ryan
> Sent: Wednesday, June 06, 2007 11:32 AM
> To: RPG programming on the AS400 / iSeries
> Subject: Re: Ovrsplf in rpgle program help
>
>
> Betcha LEN =0. Try
> Eval Len = %Len(@cmd)
>
> before the qcmdexc
>
> On 6/6/07, Willie J. Moore <WJMoore@xxxxxxxxxxxx> wrote:
> > With the help of all of you I am now getting closer.
> > I am now getting the following error: 'The call to *LIBL/QCMDEXC
> ended in error'
> > When I look at the JOBLOG the following MSG is: 'Command length not
valid'.
> > When I look at the dump, the @CMD has the correct data. How do I
> find the correct length and will I have to change it for the next
'QCMDEXC'?
> > Here is the code I am using.
> >
> > C move *blanks @cmd 23
> > C if %Open(ADITALABRP)
> > C Close ADITALABRP
> > C ENDIF
> > C*
> > C EVAL @CMD = 'DLTOVR FILE(ADITALABRP)'
> > C CALL 'QCMDEXC'
> > C PARM @CMD
> > C PARM LEN 15 5
> >
> > Thanks,
> > Willie..
> >
> > -----Original Message-----
> > From: rpg400-l-bounces@xxxxxxxxxxxx
> > [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Wayne McAlpine
> > Sent: Wednesday, June 06, 2007 10:47 AM
> > To: rpg400-l@xxxxxxxxxxxx
> > Subject: Re: Ovrsplf in rpgle program help
> >
> >
> > You will need to assign a value to LEN also. Either hard code it or
use
> > the CHECKR op code to dynamically determine the length of the command
> > string.
> >
> > Willie J. Moore wrote:
> > > I want to use the ovrsplf option in an rpgle program. I need to
> override the number of 'copies'. The number of 'copies' (labno)
> will be from a field entered on a display.
> > > Here is what I have come up with so far:
> > >
> > > F ADITALABRPO E PRINTER OFLIND(*IN91)
> > >
> > > EVAL @CMD = 'OVRSPLF FILE(ABCFILE) COPIES(LABNO)'
> > > CALL 'QCMDEXC'
> > > PARM @CMD
> > > PARM LEN
15 5
> > >
> > > C WRITE DTEORDNO
> > > C WRITE DTEORDN1
> > >
> > > I can do this in a CL program. Have the number of labels in the
> display program pass to the print program. But would like to do it
> all in one program.
> > > Any help or examples would be greatly appreciated.
> > > Thanks,
> > > William Moore
> > >
> > >
> > --
> > 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.
> >
> >
> > --
> > 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.
> >
> >
> --
> 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.
>
>
> --
> 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.
>
--
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.
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.