Re: CHGSPLFA problem maybe link to V5R1

[rob@xxxxxxxxx]

What I was trying to figure out is if the method you used for determining
the JOB parameter might have been flawed.  Example, hard coded offsets to
some user space in an API which might have gotten upgraded in 510.

Beats me why you're getting the problem.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin



                    "Denis Robitaille"
                    <DRobitaille@cascad       To:     <midrange-l@midrange.com>
                    es.com>                   cc:
                    Sent by:                  Fax to:
                    midrange-l-admin@mi       Subject:     Re: CHGSPLFA problem 
maybe link to V5R1
                    drange.com


                    02/21/2002 01:16 PM
                    Please respond to
                    midrange-l






By "look like", I ment the FILE and FORMTYPE keyword(the value I gave were
just example). I use the default value for the job which then is the
current one.

Denis Robitaille
Directeur services techniques
Cascades Inc
819 363 5187
fax 819 363 5177


>>> rob@dekko.com 02/21/02 10:10am >>>

When you said 'looks like' I am concerned.  Are you passing the JOB
parameter, or is defaulting to the current job?  If you are passing the JOB
parameter, how are you determining it?


Hello all,

I have an intermitent problem that is occuring at too of my sites that have
recently migrated to V5R1. I will try to explain the situation:

- An rpg program generate a spool file. Before finishing, the same rpg
program call QCMDEXC to execute a CHGSPLFA over the open spool file (we
want to change the form type depending on some values). The command string
looks like this:
CHGSPLFA FILE(RPGPRTF) SPLNBR(*LAST) FORMTYPE(NONSTD).

Most of the time, it works fine, but occasionnaly, I get the message
CPF3303 (File RPGPRTF not found in job //*). One funny thing I noticed is
that normally, in the message, you see the job id (number/user/device) in
the body of the message. But when my problem occurs, the job ID is //*.

Does anyone else has that kind of problem?

Any suggestion?

Denis Robitaille
Directeur services techniques
Cascades Inc
819 363 5187
fax 819 363 5177