On 27 Apr 2012 07:47, rob@xxxxxxxxx wrote:
For those of you who do not have BRMS it looks sort of like

Remote Local Remote System Network
Location Name Network ID Status Status
GDI GDI1 Online Active
GDIHQ GDI1 Online Active
<<SNIP>>

Call stack:
...
QUICMD QSYS /0605
Q1ACRMT QBRM _CL_PEP
Q1ACRMT QBRM 209 Q1ACRMT
Q1AR1RMT QBRM _QRNP_PEP_Q1AR1RMT
Q1AR1RMT QBRM 1341 Q1AR1RMT
QRNXIO QSYS 63 _QRNX_WS_EXFMT
QWSGET QSYS /065F
QT3REQIO QSYS /0253

Cranking up the joblog shows no command being used to do this.


The BRMS had\has always operated in the "user state" so whatever they have is available to anyone. Notice the called program from the UIM menu is the Q1ACRMT which calls the Q1AR1RMT, which presumably is the program that retrieves [and obviously displays] that information; obviously, using the RPG. The list of remote location names could be their own list, as registered to the BRMS, or the list from WRKRDBDIRE [which is from the data in QADBXRDBD; generally accessible via QADBXRMTNM]. Testing availability is via whatever means of comm mechanism is supported, though for "Active" one would presume by whatever mechanism is the primary access method to the target; thus if by SQL CONNECT, SBMRMTCMD, or open of a DDMF to that target location, then that status would be displayed if whichever request(s) was successful.

Not that I am recommending this... but given the code runs in the user state, it may also be in the user domain which would mean you could just CALL QBRM/Q1ACRMT the same way the UIM panel group or menu does, and the effect should be the same.

To find out what the code does to implement that feature, a trace will reveal much.

Regards, Chuck

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].