MIDRANGE dot COM Mailing List Archive



Home » MIDRANGE-L » December 2013

Re: system name in access telnet screen and user displays



fixed

On 06-Dec-2013 09:23 -0800, franz400 wrote:
The RTVNETA is one issue.
I want to verify IBM Content Manager (the 5.3 version) and other
products that may use RTVNETA or its API.

Somewhat tongue-in-cheek, because I expect few would want to or actually do so, but...

Specific to and on those systems, you possibly could write a program [that is modified to run in the system domain to enable the pgm] to change the copy of that data which is stored in every job control structure; whence the MENU surely gets the value, rather than redirecting to the system control block. The program could be called by the routing program for the interactive subsystem(s), and a scope message could be added to run at job termination in order to reset the value to the original\expected value, so that the next re-use of that job structure by any other [possibly non-interactive] job is unaffected by the deception.

Specific to and on those systems, you possibly could /Trojan Horse/ the Retrieve Network Attributes (QWCRNETA) API, the RTVNETA command, and [probably also a] non-API system program that are called to get that information... but I would expect the overall effect of that would be the same as having used CHGNETA SYSNAME(NewValue). In either case, requiring an IPL, so that every job's private copy of that information will be reflected by the pending change to the system control block that stores the System Name value; pending the completion of the next PwrDwn+IPL.






Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact