Async Operations Console: Difference between revisions
(More pinouts. Source: SY44-5965-03, PDF Page 311, fix typos, indented tables) |
(→Cables: Quick Links) |
||
| Line 11: | Line 11: | ||
== Cables == | == Cables == | ||
IBM offered mainly three cables connect a given serial IOA port to a PC: | IBM offered mainly three cables connect a given serial IOA port to a PC: | ||
* 97H7555 — for connecting to a #2609 dual port IOA with one three-row-many-pins connector, and an adapter brick, | * [[#97H7555|97H7555]] — for connecting to a #2609 dual port IOA with one three-row-many-pins connector, and an adapter brick, | ||
* 97H7556 — for connecting to a #2699 dual port IOA with two separate ports reminiscent of a DVI connector, | * 97H7556 — for connecting to a #2699 dual port IOA with two separate ports reminiscent of a DVI connector, | ||
* 97H7557 — for connecting to a #2721 dual port IOA with two separate mini-centronics style ports. | * [[#97H7557|97H7557]] — for connecting to a #2721 dual port IOA with two separate mini-centronics style ports. | ||
In addition, there were three ''remote control cables'' to support remote control of certain panel functions, such as changing IPL mode, and the like. | In addition, there were three ''remote control cables'' to support remote control of certain panel functions, such as changing IPL mode, and the like. | ||
| Line 19: | Line 19: | ||
* 97H7584 for some 6xx machines, | * 97H7584 for some 6xx machines, | ||
* a more or less 1:1 DB25 parallel port cable, | * a more or less 1:1 DB25 parallel port cable, | ||
* 97H7591 for "all other systems". | * [[#97H7591|97H7591]] for "all other systems". | ||
The ''remote control cables'' were thought for scenarios where one can use Windows RAS functionality to dial into a "console PC" remotely, to steer not only console but also the panel. I assert that this scenario is no longer relevant and only mentioned for completeness. For details, see the ''Operations Console Setup'' document. | The ''remote control cables'' were thought for scenarios where one can use Windows RAS functionality to dial into a "console PC" remotely, to steer not only console but also the panel. I assert that this scenario is no longer relevant and only mentioned for completeness. For details, see the ''Operations Console Setup'' document. | ||
Revision as of 20:41, 22 May 2023
|
This article isn't finished yet or needs to be revised. Please keep in mind that thus it may be incomplete.
Reason: Collect pinout from all three cables. |
Async Operations Console has long been a part of the AS/400. On some machines — like the P02, and P03 — it was the only way to obtain console services at all.
Basically, Async OpsCon is comprised of
- setting the machine to the correct console mode via panel,
- connecting the cable between the hardware,
- using a supporting Client Access for Windows release.
Starting with Power 5 based hardware, the service processor has been upgraded with dedicated LAN ports, and an IP stack. This is called LAN Operations Console and not handled in this article.
Cables
IBM offered mainly three cables connect a given serial IOA port to a PC:
- 97H7555 — for connecting to a #2609 dual port IOA with one three-row-many-pins connector, and an adapter brick,
- 97H7556 — for connecting to a #2699 dual port IOA with two separate ports reminiscent of a DVI connector,
- 97H7557 — for connecting to a #2721 dual port IOA with two separate mini-centronics style ports.
In addition, there were three remote control cables to support remote control of certain panel functions, such as changing IPL mode, and the like.
- 97H7584 for some 6xx machines,
- a more or less 1:1 DB25 parallel port cable,
- 97H7591 for "all other systems".
The remote control cables were thought for scenarios where one can use Windows RAS functionality to dial into a "console PC" remotely, to steer not only console but also the panel. I assert that this scenario is no longer relevant and only mentioned for completeness. For details, see the Operations Console Setup document.
It is unknown if connections require a true 16x50 based PC serial port, or USB to RS-232 adapters can be used. Further testing is necessary.
97H7555
This cable features the following connectors:
- DB-25 female for the "AS/400 end",
- DB-9 female for the "PC end".
Basically, the cable is a standard null modem async cable with pin 10 connected to ground.
DB9 DB25 1 20 2 2 3 3 4 6 5 1, 7, 10 6 20 7 5 8 4
When using this cable with a P03 machine, console is Port 2.
97H7557
This cable features the following connectors:
- A shrinked centronics-like 36-pin connector for the "AS/400 end",
- DB-9 female for the "PC end".
DB9 Centronics Comment 1, 4 15 DTR/DCD - DSR 2 13 RxD - TxD 3 6 TxD - RxD 5 7, 10, 27 Gnd 6 4 DSR - DTR 8 2 CTS - RTS 7 33 RTS - CTS
97H7591
This cable features the following connectors:
- DB-9 male for the "AS/400 end",
- DB-9 female for the "PC end".
DB9 Centronics Comment 2 2 RxD - TxD 3 3 TxD - RxD 7 7 RTS - CTS 8 8 CTS - RTS 5 5 Ground
Software
- Client Access for Windows 5.1 is 32-bit software running on Windows NT derived Windows Operating systems. It has Async Operations Console support.
- IBM i access for Windows 7.1 has no support for Async Operations Console support.
Further testing is necessary to establish scenarios for a working console connection.
See also
Weblinks
- RS-232, Wikipedia
- Operations Console Setup, SC41-5508-01
- AS/400e server 170 and 250 Problem Analysis, Repair and Parts, SY44-5965-03