Re: Spool file has different job name to job creating it -- MIDRANGE-L

Thank you for the answer.

While I can work with this and create a solution I am totally baffled why
one system behaves this way and every other system does not.

Why is this one system doing a profile swap and the others are not ?

I installed both systems. Installation was not a save on old and restore
on new, it was a restore of profiles and a data (library) migration. The
Zend install was fresh not copied.

The working system has job XTOOLKIT, type BCH with function PGM-XMLSERVICE
- The NON working system has job XMLSERVICE, type BCI with function
PGM-XMLSERVICE

How can I check the version of XMLSERVICE both in Library XMLSERVICE and
in the IFS
/usr/local/zendphp7/var/libraries/PHP_Toolkit_for_IBMI_i/default/library ?

Thanks

Don Brown

"MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> wrote on 22/10/2019
09:06:16 AM:

From: "Charles Wilt" <charles.wilt@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"

<midrange-l@xxxxxxxxxxxxxxxxxx>

Date: 22/10/2019 09:06 AM
Subject: Re: Spool file has different job name to job creating it
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxxxxxxxx>

Yep, long time "working as designed" issue for client/server apps on the

Kevin has pointed you to the best solution...

Here's an old doc that talks about the solutions...
https://www.ibm.com/support/pages/retrieving-spooled-files-
generated-host-server-job

Charles

On Mon, Oct 21, 2019 at 4:32 PM Don Brown via MIDRANGE-L <
midrange-l@xxxxxxxxxxxxxxxxxx> wrote:

I have an open PMR for this issue.

Sometimes the response you get from IBM leaves me somewhat bewildered

...

Anyway I am hoping someone on the list can suggest a solution to my

issue.

The scenario is this;

From a web page the user can click a button to open a PDF. This

button

calls a service program that then calls the print program, the spool

file

is then copied to the IFS as a PDF and the path and file name is

passed

back to the PHP script.

The PHP call to the service program is using XMLSERVICE and is using

user

PHPTSTUSER to authenticate.

So here is the problem;

The XMLSERVICE job is running in QSYSWRK with Current User (from
wrkactjob) as PHPTSTUSER.

If I use 5=Work with from the active jobs list, the user shown for the

job

is QUSER.

The qualified job name is XMLSERVICE/QUSER/367930

The program creates the spool file and the qualified name of the spool
file is QPRTJOB/PHPTSTUSER/347530. Different job name and different

job

number.

So the process that tries to copy the spool file fails because as yet

can find no way to retrieve the actual spool file name.

Running in debug the program that opens/creates the spool file has the

job

name of XMLSERVICE/QUSER/367930.

Other Information

On this machine the XMLSERVICE jobs are running in QSYSWRK and as BCI

jobs

On a different machine the jobs have a name of XTOOLKIT with a

function of

XMLSERVICE and as BCH jobs

I set both of these systems up and after much searching still can not

find

why/how to change the jobs from BCI to BCH. This must be specified in
PHP/XMLSERVICE set up somewhere but I can't find any documentation or

any

likely line in the ini files.

I believe this to be the issue as on the other system(s) the PDF has

the

same job name as the job that created it and the copy to the IFS

succeeds.

IBM's Response

Their first response was to retrieve the job name using the QUSRSPLA

API -

I did not expect this to make any difference but I tried it and no, it
made no difference - I do not have the correct qualified job name
available so using the qualified job name the job is running under

does

not retrieve any spool file.

Then after I provided more details and a step by step debug process

the

response was; So actually, there is no problem with the application

self, it works fine and as expected, BUT only fail to retrieve the

correct

job name when running in DEBUG mode, correct?.

I appreciate the support IBM provides but really ? Am I wrong or being
overly critical of the support ?

Thanks

Don Brown

______________________________________________________________________
This email has been scanned for computer viruses. Although MSD has

taken

reasonable precautions to ensure no viruses are present in this email,

MSD

cannot accept responsibility for any loss or damage arising from the

use of

this email or attachments.
______________________________________________________________________
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related

questions.

Help support midrange.com by shopping at amazon.com with our affiliate

link:

https://amazon.midrange.com

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud

service.

______________________________________________________________________

______________________________________________________________________
This email has been scanned for computer viruses. Although MSD has taken reasonable precautions to ensure no viruses are present in this email, MSD cannot accept responsibility for any loss or damage arising from the use of this email or attachments.
______________________________________________________________________