Re: iSeries running Oracle Goldengate

On 01-Jul-2016 08:17 -0500, Kevin Kimsey wrote:

On 01-Jul-2016 07:30 -0500, Kevin Kimsey wrote:

I am running :
Oracle GoldenGate Command Interpreter for DB2 for i
Version 12.2.0.1.2 OGGCORE_12.2.0.1.0_PLATFORMS_160310.1305
IBM i, ppc, 64bit (optimized), IBM DB2 for i on Mar 10 2016 23:37:00
Operating system character set identified as ISO-8859-1.

On iSeries at V7R1M0 in QP2TERM. It works very well to replicate
data between our iSeries and Oracle platforms, but the issue I am
having is the jobs that Goldengate runs get submitted to the QINTER
subsystem. How can I make them submit to QBATCH or QUSRWRK
subsystems?

What is the reasoning? They are a reflection of the work\job from which they were started [which apparently is an interactive job running in QINTER]. I expect that if the job that started them were running in QBATCH, then those jobs would also run in QBATCH.

Subsystem/Job User Type CPU % Function Status
QINTER QSYS SBS .0 DEQW
MGR AUTBRK BCI .0 PGM-mgr SELW
OGG AUTBRK BCI .0 PGM-server SELW

The Batch Immediate (BCI) jobs are the effect of the fork of the interactive requester. And as apparently named jobs "The IBM PASE for i environment specification QIBM_PASE_USE_PRESTART_JOBS=Y will be ignored when the fork400() or f_fork400() functions are used with a non-null jobname or a non-zero resourceID value." [https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_71/apis/pase_fork400.htm]

In QP2TERM - I start the Goldengate application. From there, I can
start processes by issuing GG commands - Start Manager, Start Replicat
or Start Extract.


/QOpenSys/usr/bin/-sh

GGSCI (FCDEV.FMHI.COM) 1>
> info all

Program Status Group Lag at Chkpt Time Since Chkpt

MANAGER RUNNING
EXTRACT ABENDED EXT2 00:00:00 18:45:50
EXTRACT ABENDED EXT3 00:00:00 1466:08:15
REPLICAT RUNNING REP1 00:00:00 00:00:06


GGSCI (FCDEV.FMHI.COM) 2>

===>>

Given the use of that interactive shell for input\output, the Submit Job (SBMJOB) to start the originating job [of those BCI jobs] is not an option. The originating job can start in any subsystem for which a Display Device is available, either per Allocation (AT) *SIGNON or could be entered via Transfer Job (TFRJOB) using *ENTER allocation [see Add WorkStation Entry (ADDWSE)].