Re: Device names and interactive subsystem descriptions

Thanks Jim. The entry starts with the letter "C" followed by the digit zero.

Just looked for an object lock. Device is named C059719, Object
locks are held by
BINTER (the subsystem) and QCMNARB01

Actually, BINTER status is REQ and QCMNARB01 is HELD. Did a VRYCFG
*OFF and back on reset set to *YES. No change. But, I am guessing
that the reason for no change was no attempt to use it.

I think I found it, maybe. The other entries I looked at in the two
subsystems are set for control job at *ENTER. The one I added is set
to *SIGNON.

More thought....... BINTER and BINTER2 have smae prefixes. Entries
appear to have *SIGNON in one subsystem and *ENTER in the other. I
remember that now. Believe it was just a matter of adding the entry
into the other subsystem with the other value. Been too long since I
have done this.

Definitely would explain why it didn't work as the entry was ambigous.

John McKee

On Fri, Feb 3, 2012 at 5:35 PM, Jim Oberholtzer <midrangel@xxxxxxxxxx> wrote:

The subsystem does not need to be restarted for a workstation entry to
take effect.

I am confused about the "C0".  Workstation IDs cannot start with a
number.  Did you start them literally with "C0"

In any case the subsystem does not need to restart to enable a
workstation entry.  One thing that might be happening.  If another
subsystem grabs the device and allocates it, then it might hang onto it
until the device is varied off and back on.  I just tried that on our
system at iDevCloud and was able to mimic what you are describing.
Try varying the devices off and then back on with the new subsystem
entry active.

I would also look into the other workstation entries to be sure there is
not a similar entry out there.

Jim Oberholtzer
Chief Technical Architect
Agile Technology Architects


On 2/3/2012 5:11 PM, John McKee wrote:

For a long time, there were standards where I work as to naming
conventions for devices.  But, since the system is on the way out in
maybe a year, other people are dictating things.

In the case of the above, the person who assists others establishing a
remote connection through the firewall has decided that it would be
easier if the device name was same as the user id.

We have two interactive subsystems.  Each has a number of workstation
entries - composed of three characters followed by an asterisk.

I had forgotten about those entries when I created device descriptions
that start with C0 (a digit zero).

My day off today, and I received a call from work that the remote
users only got a blank screen.  So, I added the C0* entry.  I was told
later that it still did not work.

I am guessing that the subsystem needed to be restarted for the change
to take effect.  Am I right, or is there something else that needs to
be done?

John McKee
--

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.