Salesforce

Broker Subsystem Configuration (Magic xpa 3.x)

« Go Back

Information

 
Created ByKnowledge Migration User
Approval Process StatusPublished
Objective
Description

Broker Subsystem Configuration (Magic xpa 3.x)

To use the Magic xpa Request Broker, you need to configure the Broker in the MAGIC subsystem:

  1. Select the Magic Config. menu option.

  2. Select Option 6, Broker Subsystem Confg., to create the Broker job description, job queue, and job class in the BROKER Subsystem Confg. screen.

At this stage, JOBQ MGBROKER and a routing entry for the MGBROKER job are added to a selected subsystem description.

MGBROKER JOBQ is a default job for the Magic xpa broker jobs. When you start a broker job using STRMRBRUN, the job is submitted to JOBQ MGBROKER. The routing entry sets a job class and a memory pool of the system main storage where the MGBROKER job is going to run. By default, it is set for the MGBROKER job class and storage pool 1.

The following job properties are controlled by the job class: Run priority, Time slice in milliseconds, Eligible for purge, Default wait time in seconds, Maximum CPU time in milliseconds, Maximum temporary storage in megabytes, and Maximum threads. You can manually change them during the job performance tuning by using the CHGCLS IBM i command.

For example: CHGCLS CLS([Magic install directory]/MGBROKER) RUNPTY(XX) TIMESLICE(XXXX) CPUTIME(*NOMAX) MAXTMPSTG(*NOMAX) MAXTHD(*NOMAX).

The routing entry is linked with a job description via the Compare value property of the routing entry and the Routing data property of the job description. When the MGBROKER job enters the subsystem via JOBQ, the operating system validates the Routing data of the job description against the Compare value of the routing entries in the subsystem. When the match is found, the job’s memory pool is assigned and the relevant job properties are applied to the job according to the routing entry settings.

Make sure that the subsystem is not active when you configure it via the menu.

For security reasons, this step is allowed only when the subsystem is not active.

Make sure that you do not have jobs pending in the job queue.

As an alternative to the configuration menu, you can use the IBM i ADDJOBQE or RMVJOBQE and ADDRTGE or RMVRTGE commands for Magic xpa broker configuration.

  1. Connect JOBQ to subsystem:

ADDJOBQE SBSD(SBSLIB/SBSNAME) JOBQ(<Magic install directory>/MGBROKER) MAXACT(1) SEQNBR(20)

Where:

SBSLIB – name of the subsystem library

SBSNAME – subsystem name

<Magic install directory> – name of the Magic xpa installation

1 – maximum number of concurrently active jobs

20 – job sequence number in subsystem property. The next available number can be found using the WRKSBSD command:

WRKSBSD SBSLIB/SBSNAME

option 5 (Display)

option 6 (Display Job Queue Entries)

  1. Disconnect JOBQ from the Subsystem:

    RMVJOBQE SBSD(SBSLIB/SBSNAME) JOBQ([Magic install directory]/MGBROKER)

  2. Add a Routing entry:

    ADDRTGE SBSD(SVRLIB/SBSNAME) SEQNBR(20) CMPVAL(UNI19LB.MGRNT) PGM(QCMD) CLS(SVRLIB/MGBROKER)

  3. Remove a Routing entry:

    RMVRTGE SBSD(SVRLIB/SBSNAME) SEQNBR(10)

  4. If there's an error, verify the joblog using the DSPJOB option 10.

Reference
Attachment 
Attachment