Try-AS/400 - Recent changes [en]

UNIX-User's Cheater Table

PoC — Sun, 12 Jul 2026 16:55:47 GMT

Added whoami example

← Older revision		Revision as of 18:55, 12 July 2026
Line 136:		Line 136:
	\|valign="top"\|<code>mysql</code>,<br /><code>isql</code>		\|valign="top"\|<code>mysql</code>,<br /><code>isql</code>
	\|valign="top"\|<code>strsql</code>		\|valign="top"\|<code>strsql</code>
	\|valign="top"\|Not limited to ''mysql'' ~~that is~~ more like a placeholder for any command line client accessing a database for entering SQL queries directly.		\|valign="top"\|Not limited to ''mysql'', but more like a placeholder for any command line client accessing a database for entering SQL queries directly.
			\|-
			\|valign="top"\|<code>whoami</code>
			\|valign="top"\|<code>dspjob</code>
			\|valign="top"\|
	\|}		\|}

Communications Traces

PoC — Sat, 11 Jul 2026 11:05:20 GMT

Note

← Older revision		Revision as of 13:05, 11 July 2026
(2 intermediate revisions by the same user not shown)
Line 1:		Line 1:
	'''Communications Traces''' are essentially very much akin to ''tcpdump'' or ''Wireshark'' on common platforms. It's a multi-step, non-interactive process.		'''Communications Traces''' are essentially very much akin to ''tcpdump'' or ''Wireshark'' on common platforms. It's a multi-step, non-interactive process.

			<blockquote>'''Note:''' Command are examples and must be tailored to your particular environment!</blockquote>

	* Start trace. Network traces are always taken from a line description object.		* Start trace. Network traces are always taken from a line description object.
Line 7:		Line 9:
	endcmntrc cfgobj(trnline) cfgtype(*lin)		endcmntrc cfgobj(trnline) cfgtype(*lin)
	* Format a report from the trace data. Goes to the standard printer queue.		* Format a report from the trace data. Goes to the standard printer queue.
	prtcmntrc cfgobj(trnline) cfgtype(lin~~) sltctld(fiona~~) fmttcp(no) fmtbcd(*no)		prtcmntrc cfgobj(trnline) cfgtype(lin) fmttcp(no) fmtbcd(*no)
	* Delete now unneeded Trace Data.		* Delete now unneeded Trace Data.
	dltcmntrc cfgobj(trnline) cfgtype(*lin)		dltcmntrc cfgobj(trnline) cfgtype(*lin)

			Optionally, this trace can be exported to a database file, to be e. g. downloaded via FTP for further treatment.
			crtpf file(mylib/qpcsmprt) rcdlen(132)
			cpysplf file(qpcsmprt) tofile(mylib/qpcsmprt) splnbr(1)

	[[Category: System Administration]]		[[Category: System Administration]]
	[[Category: System Internals]]		[[Category: System Internals]]

Communications Traces

PoC — Tue, 07 Jul 2026 13:50:30 GMT

new

New page

'''Communications Traces''' are essentially very much akin to ''tcpdump'' or ''Wireshark'' on common platforms. It's a multi-step, non-interactive process.

* Start trace. Network traces are always taken from a line description object.
strcmntrc cfgobj(trnline) cfgtype(*lin) maxstg(16M) usrdta(*max) trcfull(*stoptrc)
* Run your commands for generating traffic.
* Stop trace.
endcmntrc cfgobj(trnline) cfgtype(*lin)
* Format a report from the trace data. Goes to the standard printer queue.
prtcmntrc cfgobj(trnline) cfgtype(*lin) sltctld(fiona) fmttcp(*no) fmtbcd(*no)
* Delete now unneeded Trace Data.
dltcmntrc cfgobj(trnline) cfgtype(*lin)

[[Category: System Administration]]
[[Category: System Internals]]

PCI-FSIOP Cable

PoC — Sun, 28 Jun 2026 21:09:21 GMT

English

← Older revision		Revision as of 23:09, 28 June 2026
Line 1:		Line 1:
	[[File:Ibm_45H2433_ps2.jpg\|thumb\|right\|PS/2- and ~~Seriell~~-Brick]]		[[File:Ibm_45H2433_ps2.jpg\|thumb\|right\|PS/2- and serial-Brick]]
	[[File:IPCS-2850-12.jpg\|thumb\|right\|IPCS #2850 Primary board featuring a 333 MHz Pentium Overdrive processor]]		[[File:IPCS-2850-12.jpg\|thumb\|right\|IPCS #2850 Primary board featuring a 333 MHz Pentium Overdrive processor]]
	[[File:IPCS-285A.jpg\|thumb\|right\|Daughter-card for the #2850 carrying ports and further PC chipset components]]		[[File:IPCS-285A.jpg\|thumb\|right\|Daughter-card for the #2850 carrying ports and further PC chipset components]]

PCI-FSIOP Cable

PoC — Sun, 28 Jun 2026 21:08:56 GMT

New

New page

[[File:Ibm_45H2433_ps2.jpg|thumb|right|PS/2- and Seriell-Brick]]
[[File:IPCS-2850-12.jpg|thumb|right|IPCS #2850 Primary board featuring a 333 MHz Pentium Overdrive processor]]
[[File:IPCS-285A.jpg|thumb|right|Daughter-card for the #2850 carrying ports and further PC chipset components]]
The add-on hardware '''internal PC server''', or '''IPCS''', or '''internal xSeries server''', or '''internal Netfinity server''', or '''FSIOP''', or '''File Server I/O Processor''', Feature #285x or #286x or similar require a special cable to connect essential human interface devices such as keyboard and mouse. IBM part number is 45H2433.

The connector on the board side is a Mini-Centronics with 40 pins (MDR40). Breakout-boards are available from some vendors, but no single plug, or cable to create a fan-out yourself.

This is the pinout of the IBM 45H2433 cable:
{| class="wikitable"
!rowspan="2"|IPCS<br />MDR40
!rowspan="2"|RS-232 serial<br />DE9
!colspan="2"|PS/2 (Mini-DIN 8)
!rowspan="2"|IEEE 1284 parallel<br />DB25
!rowspan="2"|Remark
|-
!Keyboard
!Mouse
|-
|align="center"|1
| 
| 
| 
|align="center"|8
|Data6
|-
|align="center"|2
| 
| 
| 
|align="center"|18
|GND
|-
|align="center"|3
| 
| 
| 
|align="center"|7
|Data5
|-
|align="center"|4
| 
| 
| 
|align="center"|1
|HostClock
|-
|align="center"|5
| 
| 
| 
|align="center"|6
|Data4
|-
|align="center"|6
| 
| 
| 
|align="center"|17
|1284 Active
|-
|align="center"|7
| 
| 
| 
|align="center"|5
|Data3
|-
|align="center"|8
| 
| 
| 
|align="center"|16
|NReverseRequest
|-
|align="center"|9
| 
| 
| 
|align="center"|4
|Data2
|-
|align="center"|10
| 
| 
| 
|align="center"|15
|PeriphRequest
|-
|align="center"|11
| 
| 
| 
|align="center"|3
|Data1
|-
|align="center"|12
| 
| 
| 
|align="center"|14
|HostAck
|-
|align="center"|13
| 
| 
| 
|align="center"|2
|Data0
|-
|align="center"|14
|align="center" colspan="5"|NC
|-
|align="center"|15
| 
|align="center"|5
| 
| 
|Clock
|-
|align="center"|16
|align="center"|5
|align="center"|3
|align="center"|3
| 
|Gnd
|-
|align="center"|17
|align="center"|8
| 
| 
| 
|CTS
|-
|align="center"|18
|align="center"|3
| 
| 
| 
|TxD
|-
|align="center"|19
|align="center"|6
| 
| 
| 
|DSR
|-
|align="center"|20
|align="center"|1
| 
| 
| 
|DCD
|-
|align="center"|21
| 
| 
| 
|align="center"|22
|GND
|-
|align="center"|22
| 
| 
| 
|align="center"|9
|Data7
|-
|align="center"|23
| 
| 
| 
|align="center"|21
|GND
|-
|align="center"|24
| 
| 
| 
|align="center"|24
|GND
|-
|align="center"|25
| 
| 
| 
|align="center"|13
|X-Flag
|-
|align="center"|26
| 
| 
| 
|align="center"|20
|GND
|-
|align="center"|27
| 
| 
| 
|align="center"|12
|NAckReverse
|-
|align="center"|28
| 
| 
| 
|align="center"|23
|GND
|-
|align="center"|29
| 
| 
| 
|align="center"|11
|PeriphAck
|-
|align="center"|30
| 
| 
| 
|align="center"|25
|GND
|-
|align="center"|31
| 
| 
| 
|align="center"|10
|PeriphClock
|-
|align="center"|32
| 
| 
| 
|align="center"|19
|GND
|-
|align="center"|33
| 
| 
|align="center"|1
| 
|Data
|-
|align="center"|34
| 
| 
|align="center"|5
| 
|Clock
|-
|align="center"|35
| 
|align="center"|1
| 
| 
|Data
|-
|align="center"|36
| 
|align="center"|4
|align="center"|4
| 
|VCC
|-
|align="center"|37
|align="center"|9
| 
| 
| 
|RI
|-
|align="center"|38
|align="center"|4
| 
| 
| 
|DTR
|-
|align="center"|39
|align="center"|7
| 
| 
| 
|RTS
|-
|align="center"|40
|align="center"|2
| 
| 
| 
|RxD
|}

Thanks to Mathias for his help when probing the pinout of an existing cable!

== Weblinks ==
* Pinouts for standard PC ports at pinouts.ru:
** [http://pinouts.ru/SerialPorts/Serial9_pinout.shtml PC serial port (RS-232 DE9) pinout]
** [http://pinouts.ru/Inputs/KeyboardPC6_pinout.shtml Keyboard PS/2 pinout]
** [http://pinouts.ru/Inputs/PS2Mouse_pinout.shtml Mouse (PS/2) pinout]
** [http://pinouts.ru/ParallelPorts/ParallelECP_pinout.shtml ECP Parallel LPT port (IEEE-1284A) pinout]
* [https://www.ibm.com/support/knowledgecenter/en/POWER6/iphah/cablesandcards.htm Connectors and adapters] bei IBM.com

[[Category: Hardware Documentation]]

File:Ibm 45H2433 ps2.jpg

PoC — Sun, 28 Jun 2026 21:01:29 GMT

PoC uploaded File:Ibm 45H2433 ps2.jpg Own photography

New page

== Summary ==
Own photography

Configuring the OS/400 DNS server without OpNav

PoC — Sun, 28 Jun 2026 19:53:51 GMT

New

New page

The '''OS/400 DNS server''' can officially be configured via '''OpNav''' only. However, there are other ways…

OpNav is a component of ClientAccess for Windows, which is installed along with OS/400.

== Configuration ==
The DNS server of OS/400 V4R2 up to and including V4R5 is based on BIND 4.9.3 from the ISC. Therefore, the configuration directives from ISC apply immediately. At startup, the system looks for the main configuration file ''/QIBM/USERDATA/OS400/DNS/BOOT''. You can easily create this file yourself:

Dns DNS von OS/400 V4R2 bis einschliesslich V4R5 basiert auf BIND 4.9.3 vom ISC. Somit gelten auch die Konfigurationsdirektiven unmittelbar. Beim Start wird nach der Hauptkonfiguratiosndatei ''/QIBM/USERDATA/OS400/DNS/BOOT'' gesucht. Diese kann man bequem selbst erstellen:
edtf '/qibm/userdata/os400/dns/boot'

Example file content:
; Working Directory
directory /QIBM/USERDATA/OS400/DNS
; Root-DNS-File
cache . NAMED.ROOT
; Zone Statements
secondary myzone.com 192.168.1.11 db.myzone.com

''Edtf'' is very similar to ''seu'' in its operation . Alternatively, this file can be created elsewhere and uploaded to the appropriate location in ASCII mode via FTP.

It is recommended to import an up-to-date root zone file. This can be obtained, for example, from [https://www.internic.net/domain/named.root Internic], and transferred via FTP to ''qdns/qatocdnsrv.root'' as well as to ''/qibm/userdata/os400/dns/root.hint'', as specified in the corresponding directive.<ref>BIND cannot deal with a file in a library. It's unclear why there is a copy in a ''qsys.lib'' file.</ref>

The directory permissions must be adjusted before starting the DNS server:
strqsh cmd('chown qtcp /qibm/userdata/os400/dns')

Through the <code>chgdnsa</code> command, you can set ''autostart at TCP startup'' to ''*yes'', as well as a desired debug level, and finally issue <code>strtcpsvr *dns</code> to start the server.

Less encouraging is the fact that when testing this DNS as a secondary to BIND 9.10.3 running on Debian Linux, no secondary zones can be loaded. The primary server pushes the zones out via AXFR, but the slave on the AS/400 does not accept them. According to the AXFR job log, BIND expects more data bytes than it receives. A fix to this behavior is not known.

== Weblinks ==
* [http://www.cs.ait.ac.th/~on/O/oreilly/tcpip/dnsbind/ch04_03.htm Setting Up a BIND Configuration File], O'Reilly Books
* [https://www.redbooks.ibm.com/redbooks/pdfs/sg245147.pdf AS/400 TCP/IP Autoconfiguration: DNS and DHCP Support], IBM RedBooks

[[Category: Software Configuration Guide]]
[[Category: System Administration]]

← Older revision		Revision as of 18:55, 12 July 2026
Line 136:		Line 136:
	\|valign="top"\|<code>mysql</code>,<br /><code>isql</code>		\|valign="top"\|<code>mysql</code>,<br /><code>isql</code>
	\|valign="top"\|<code>strsql</code>		\|valign="top"\|<code>strsql</code>
	\|valign="top"\|Not limited to ''mysql'' ~~that is~~ more like a placeholder for any command line client accessing a database for entering SQL queries directly.		\|valign="top"\|Not limited to ''mysql'', but more like a placeholder for any command line client accessing a database for entering SQL queries directly.
			\|-
			\|valign="top"\|<code>whoami</code>
			\|valign="top"\|<code>dspjob</code>
			\|valign="top"\|
	\|}		\|}