Using IBM i? Need to create Excel, CSV, HTML, JSON, PDF, SPOOL reports? Learn more about the fastest and least expensive tool for the job: SQL iQuery.
When I sign onto a remote AS400 through Client Access, my interactive job get placed into a particular subsystem. I have a need for my interactive session to go to the system console, so I can monitor the system and recover from abnormal ends when something like a savnosys takes place.
Where in the chain does this occur; through client access during sign on, through a set up off the job description of my sign on, or can this be done at all?
Thanks in advance.
Don't you have to do a TFRCTL TFRJOB to the other subsystem after you sign on?
Been a while, I could be wrong.
TFRJOB, not TFRCTL. You need to know the name of a job queue in the target subsystem. If your controlling subsystem is QCTL, the job queue is also QCTL, so:
TFRJOB QCTL
Another option would be to define your 5250 session with a specific device name, and add a workstation name entry to the subsystem at *SIGNON. Then that session would start in the subsystem, eliminating the need for the TFRJOB.
Bob,
When I tried to use TFRCTL from the command line during my interactive session, I get this error message;
Command TFRCTL not allowed in this setting.
btw, to answer the general question, assignment of a workstation device to a subsystem is based on the subsystem's workstation entries. You can assign workstations to a subsystem by name, specific or generic, or by device type. Device type can be specific, such as 3179, 3476, ..., or there are special values including *ALL and *CONS.
IBM supplied subsystem QCTL has entries for *CONS *SIGNON and *ALL *ENTER, and QINTER has entries *CONS *ENTER and *ALL *SIGNON. So QCTL allocates the console (*CONS) for signon, but allows all others to enter QCTL via TFRJOB. QINTER allocates all workstations for signon, and allows the console to transfer in.
The order you start the subsystems is important. The subsystem that starts first gets the first shot at allocating the workstation device. A subsystem with *ALL should be started after any that have more specific entries.
Starting a subsystem only attempts to allocate workstations that match a *SIGNON entry. *ENTER devices are not allocated up front; they're there to allow for later TFRJOB. If a suitable *ENTER entry is not available, you cannot transfer into that subsystem. (Try TFRJOB QBATCH. Unless you've done something weird, you should get a message that subsystem QBATCH has no usable work station entries.)
Thanks, Dale, I was using TRFCTL instead of TRFJOB. Once I used TRFJOB, my interactive job went from the subsystem I was signed onto to the QCTL subsystem.
another option would be to install something like logmein on this main console (assuming it is a pc). Then you don't need anything but a browser to hit it). So if you are at the superbowl and you need to log in, you get on your iphone and ...