RE: Web services behavior

Journaling is a Db2 function and not something your program would typically affect (barring extraordinary actions).

When you recompile a program, it's possible that jobs that have already activated that program will continue to use the old version (depending on things like activation group and *inLR).

You mention Apache, are these CGI programs?




-----Original Message-----
From: Merlino, Basilio [mailto:b.merlino-nisext@xxxxxxxxx]
Sent: Saturday, February 24, 2018 4:06 AM
To: rpg400-l@xxxxxxxxxxxx
Subject: Web services behavior

Dear All
Let's me describe the following scenario.
Program A is called by a web service request Program A in one point call a second program “B"
Program "B" have 2 file under journal and write on it On Tuesday I have recompile pgm B without end the apache server and I was wondering to discover (on Wednesday) that all the transactions was not written on the file defined in program "B"
Initially I was thinking a bug on the program but neither Wednesday and the day after I faced the problem I didn't find any kind of log so my question is this behavior is correct? It's seem that the ws "lost" the program. It's mandatory to close and restart the server Why as happen in a normal case new object is not use?
Thanks to all for your answers
Basilio

***********************************************************************************************************
CONFIDENTIALITY NOTICE

This message is for the named person's use only. It may contain confidential, proprietary or legally privileged information.

If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify us by email to email.security@xxxxxxxxxxxxxxxxx with a copy of this message. You must not, directly or indirectly, use, disclose, distribute, print or copy any part of this message if you are not the intended recipient. NISSAN EUROPE and any of its subsidiaries each reserves the right to monitor all e-mail communications through its networks.

NISSAN EUROPE is neither liable for the proper, complete transmission of the information contained in this communication nor any delay in its receipt. This email was scanned for the presence of computer viruses. In the unfortunate event of infection NISSAN EUROPE does not accept liability.

Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorised to state them.

***********************************************************************************************************