Re: PDF file problems - Problem known!

>> how can I join two CL variables together trimming out the extra spaces? I
would like to avoid trimming all
> > the field sizes down if possible.

like this? exuse the hardcode part, and use just variables. I'm building a
pdf file name using &paid is unique to
the customer requesting, and timestamp and '.pdf'. If you have garbage in
the variables this won't work-if blanks, no problem.
 CHGVAR     VAR(&URL) VALUE('/bncf/' *TCAT &PAID *TCAT &TIME *TCAT '.pdf')
jim

----- Original Message -----
From: "Phil" <sublime78ska@yahoo.com>
To: <midrange-l@midrange.com>
Cc: <MNWills@taylorcorp.com>
Sent: Tuesday, August 21, 2001 8:23 PM
Subject: RE: PDF file problems - Problem known!


> Save yourself the headache and use an RPG program, either just to
> concatenate the variable or to do that and use qcmdexc to call the chgaut
> cmd.
>
> Phil
>
> > -----Original Message-----
> > From: midrange-l-admin@midrange.com
> > [mailto:midrange-l-admin@midrange.com]On Behalf Of Wills, Mike N. (TC)
> > Sent: Tuesday, August 21, 2001 5:37 PM
> > To: 'midrange-l@midrange.com'
> > Subject: RE: PDF file problems - Problem known!
> >
> >
> > Okay...for any of you here is what the problem truly is. On my CHGAUT
> > command, the path _is_ incorrect. I run into that longer than 32
character
> > parm passed to a CL problem, so I have extra data bleeding into the
field.
> >
> > What I am wondering now is, how can I join two CL variables together
> > trimming out the extra spaces? I would like to avoid trimming all
> > the field
> > sizes down if possible.
> >
> > Thanks for your help so far Peter.
> >
> > Mike Wills
> > IT Corporate Support
> > MNWills@taylorcorp.com
> >
> >
> > -----Original Message-----
> > From: Wills, Mike N. (TC) [mailto:MNWills@taylorcorp.com]
> > Sent: Tuesday, August 21, 2001 1:17 PM
> > To: 'midrange-l@midrange.com'
> > Subject: RE: PDF file problems
> >
> >
> > The reason for the second delay job was for troubleshooting, we
> > thought the
> > file wasn't out on the IFS at that point. I am going to be monitoring
the
> > jobs next time they process it, hopefully we can find out why.
> >
> > Mike Wills
> > IT Corporate Support
> > MNWills@taylorcorp.com
> >
> >
> > -----Original Message-----
> > From: Peter Dow [mailto:pcdow@yahoo.com]
> > Sent: Tuesday, August 21, 2001 12:45 PM
> > To: midrange-l@midrange.com
> > Subject: Re: PDF file problems
> >
> >
> > Hi Mike,
> >
> > First, SPL2STMF runs interactively, so no need for the DLYJOB -- your
> > program will not receive control until SPL2STMF is finished, one way or
> > another.  SPL2STMF does not pass errors back up the line, it
> > simply ignores
> > them, so you can't tell if it did what you expected or not.
> > Personally, I'd
> > rather it simply let the error occur - makes it much easier to find the
> > problem.
> >
> > Have you checked the job log yet when it fails?  The actual error should
> > still show up there.
> >
> > _______________________________________________
> > 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
> > _______________________________________________
> > 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
> >
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
> _______________________________________________
> 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
>