Try-AS/400 - User contributions [en]

UNIX-User's Cheater Table

2026-07-12T16:55:47Z

PoC: Added whoami example

This table lists commands available in the ''CL-Environment'', the classical OS/400-Shell, so to say. These do '''not''' apply to ''QSH'' or ''PASE'', that are UNIX-like environments within OS/400.

{|class="wikitable"
!UNIX Command
!OS/400 Equivalent
!Remarks
|-
|colspan="3"|'''Files and File System'''
|-
|valign="top"|<code>cat</code>
|valign="top"|<code>cpyf</code>
|valign="top"|Since OS/400 has no concept of stdin/stdout, these functions of cat don't apply here.
|-
|valign="top"|<code>cd</code>
|valign="top"|<code>chgcurlib</code>
|valign="top"| 
|-
|valign="top"|<code>chmod</code>
|valign="top"|<code>chgaut</code>,<br /><code>grtobjaut</code>,<br /><code>rvkobjaut</code>
|valign="top"| 
|-
|valign="top"|<code>chown</code>,<br /><code>chgrp</code>
|valign="top"|<code>chgobjown</code>,<br /><code>chgobjpgp</code>
|valign="top"| 
|-
|valign="top"|<code>cp</code>
|valign="top"|<code>crtdupobj</code>
|valign="top"| 
|-
|valign="top"|<code>dump</code>,<br /><code>tar c</code>
|valign="top"|<code>sav(lib|obj| )</code>
|valign="top"| 
|-
|valign="top"|<code>ls</code>
|valign="top"|<code>dspobjaut</code>,<br /><code>wrklib</code>,<br /><code>wrkobj</code>
|valign="top"|Shows a scrollable list of selected objects, helps in modifying access rights.
|-
|valign="top"|<code>mv</code>
|valign="top"|<code>rnmobj</code><br /><code>movobj</code>
|valign="top"| 
|-
|valign="top"|<code>restore</code>,<br /><code>tar [x|t]</code>
|valign="top"|<code>rst(lib|obj| )</code>,<br /><code>dspsavf</code>,<br /><code>dsptap</code>
|valign="top"| 
|-
|valign="top"|<code>test -f</code>
|valign="top"|<code>chkobj</code><br /><code>chkifsobj</code>
|valign="top"| 
|-
|valign="top"|<code>vi</code>
|valign="top"|<code>strseu</code> for source physical files,<br /><code>edtf</code> for stream files,<br /><code>strdfu option(5)</code> for database files.
|valign="top"|See [[Filesystems and Files on the AS/400]] for details. See [[IBM HTTP-Server for AS/400 Configuration]] for specialised command regarding web server config.
|-
|colspan="3"|'''Memory and Processes'''
|-
|valign="top"|<code>free</code>
|valign="top"|<code>wrkshrpool</code>
|valign="top"|This is for displaying the amount of built-in RAM.
|-
|valign="top"|<code>crontab -e</code><br /><code>at</code> (scheduler)
|valign="top"|<code>wrkjobscde</code><br /><code>sbmjob</code><br /><code>wrkjobq qbatch</code>
|valign="top"| 
|-
|valign="top"|<code>ps aux</code>,<br /><code>ps -edf</code>,<br /><code>top</code>
|valign="top"|<code>wrkactjob</code>,<br /><code>wrksysact</code>
|valign="top"| 
|-
|colspan="3"|'''Disk and I/O'''
|-
|valign="top"|<code>df</code>
|valign="top"|<code>strsst</code>
|valign="top"|Access to precise disk space stats is available within ''system service tools'' only.
|-
|valign="top"|<code>fsck</code>
|valign="top"|<code>rclstg</code>
|valign="top"|System needs to be in restricted mode.
|-
|valign="top"|<code>iostat -x</code>
|valign="top"|<code>wrkdsksts</code>
|valign="top"| 
|-
|valign="top"|<code>vmstat</code>
|valign="top"|<code>dspsyssts</code>
|valign="top"|Choose view option ''3'' after pressing <code>F19</code>.
|-
|colspan="3"|'''Networking'''
|-
|valign="top"|<code>ping</code>,<br /><code>aping</code>
|valign="top"|<code>ping</code>
|valign="top"|Surprise, command has same name!<br />The latter is for SNA APPN.
|-
|valign="top"|<code>netstat</code>,<br /><code>wrkappnsts</code>
|valign="top"|<code>netstat</code>
|valign="top"|Surprise, command has same name!<br />The latter is for SNA APPN.
|-
|colspan="3"|'''Development'''
|-
|valign="top"|<code>cc</code>
|valign="top"|<code>crtcmod</code>
|valign="top"|Create Object File from C-Source.
|-
|valign="top"|<code>ld</code>
|valign="top"|<code>crtpgm</code>,<br><code>crtsrvpgm</code>
|valign="top"|Create runnable Program from Object File(s),<br>create Service Program ("Shared Library") from Object File(s).
|-
|valign="top"|<code>make</code>
|valign="top"| 
|valign="top"|There is a crude port of ''make'' in the QUSRTOOLS library called [[Setting up TMKMAKE|TMKMAKE]]. See ''QUSRTOOLS/QATTINFO.TMKINFO'' for details.<ref>See also [https://www.mcpressonline.com/programming-other/general/programming-with-make-on-the-as400-part-i Programming with Make on the AS/400, Part I], and [https://www.mcpressonline.com/programming-other/general/programming-with-make-on-the-as400-part-2 Programming with Make on the AS/400, Part 2] on McPress Online.</ref>
|-
|valign="top"|<code>configure</code>
|valign="top"| 
|valign="top"|No equivalent to GNU autoconf. Possible workaround: Manually tailored, static, universal ''config.h'' for each OS-Release (Compiler Version) based on existing documentation and/or manual tests.
|-
|valign="top"|<code>diff</code>
|valign="top"|<code>cmppfm</code>
|valign="top"| 
|-
|valign="top"|<code>patch</code>
|valign="top"|<code>mrgsrc</code>
|valign="top"| 
|-
|colspan="3"|'''Other Topics'''
|-
|valign="top"|<code>lpq</code>
|valign="top"|<code>wrkoutq</code>
|valign="top"|Displays all configured printer queues and count of entries.
|-
|valign="top"|<code>mailx</code>
|valign="top"|<code>dspmsg</code>,<br /><code>snddst</code>
|valign="top"|Cron and at send mail if there was output. OS/400 sends ''messages'' and generates printer output (spooled file). Sending (SMTP) mail from the command line utilises a completely different facility.
|-
|valign="top"|<code>mt</code>
|valign="top"|<code>dsptap</code>, <code>chktap</code>
|valign="top"| 
|-
|valign="top"|<code>mysql</code>,<br /><code>isql</code>
|valign="top"|<code>strsql</code>
|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"| 
|}

The table will be expanded over time.

== See also ==
* [[Basic Commands]]

== Footnotes ==
<references/>

[[Category: Basic Knowledge‏]]

Communications Traces

2026-07-11T11:05:20Z

PoC: Note

'''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.
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) fmttcp(*no) fmtbcd(*no)
* Delete now unneeded Trace Data.
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 Internals]]

Communications Traces

2026-07-09T12:03:55Z

PoC: Local copy

'''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) fmttcp(*no) fmtbcd(*no)
* Delete now unneeded Trace Data.
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 Internals]]

Communications Traces

2026-07-07T13:52:23Z

PoC: Typo

'''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]]

Communications Traces

2026-07-07T13:50:30Z

PoC: new

'''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

2026-06-28T21:09:21Z

PoC: English

[[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-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]]

PCI-FSIOP Cable

2026-06-28T21:08:56Z

PoC: New

[[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

2026-06-28T21:01:29Z

PoC: Own photography

== Summary ==
Own photography

Configuring the OS/400 DNS server without OpNav

2026-06-28T19:53:51Z

PoC: New

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]]

IBM BOOK format

2026-06-12T22:05:26Z

PoC: /* Internal structure */ More precise

{{FIXME|Rework, add information}}
'''IBM BookManager Softcopy''' is IBM's legacy online documentation system, created in the 1980s. It was historically used mostly on mainframes, midrange (AS/400) and OS/2, although it also saw some use in other areas including AIX.

IBM no longer uses it for new documentations of its products, but there is an immense quantity of legacy electronic documentation from the period when IBM actively used it (from the 1980s thru 2010s), particularly documentation CD-ROMs/DVD-ROMs and images thereof.

The file-internal format apparently is called IBMIDDOC.

The standard DOS style extension is <code>BOO</code>, and "application/book" is sometimes used as MIME type, but was never officially registered.

== Internal structure ==
The header of BOO files sometimes contains an EBCDIC copyright notice (this is true even for books for ASCII-based platforms such as OS/2). The file contents is almost certainly also in EBCDIC, but is not readable beyond the header. Most likely this due to compression with an unknown algorithm (a relative of IBM's well-known proprietary algorithm such as TERSE?). However, the data seems too repetitive to be compressed–possibly it is just some obfuscation mechanism then?

* Bytes 1-2: unknown 2 bytes probably flags. second byte never zero, first byte often is (but not always). probably not a size, since 0001 is a common value.
* Bytes 3-6: these 4 bytes appear to always be zero
* Bytes 7: unknown, can be zero, probably more flags???
Bytes 8+: EBCDIC copyright string. Can start with one or more EBCDIC spaces (0x40), sometimes also (0xB4) (some kind of control character?)

The header is 256 bytes long. The copyright string is padded to the end of the header with 0x40 (EBCDIC space). However, it seems to have a null terminator (0x00) at the end of the actual text, before the space padding.

What follows from 256 bytes onwards looks like it could be some kind of compression dictionary, maybe a modified TERSE algorithm?

<s>It looks like the file is composed of 256 byte records (so file size should be an integer multiple of 256), often with some all-zeros records appended to the end.</s>

There is weak evidence that the file format might be record oriented with 4096 byte records: IBM upload instructions into MVS datasets hint towards that. All known files so far have a file size which can be divided by 4096 without remainder. If the file size doesn't match, it's padded with binary zeros.

== See also ==
* [[Reviving InfoSeeker]]

== Weblinks ==
* [http://www.edm2.com/index.php/BookManager BookManager Releases] contains history of IBM BookManager releases
* [https://www.ibm.com/support/pages/using-pdfs-and-bookmanager-books-your-workstation-or-mainframe Using PDFs and BookManager Books on your workstation or mainframe], IBM.com
* [https://en.wikipedia.org/wiki/Terse_(file_format) Terse (file format)], Wikipedia
* [https://en.wikipedia.org/wiki/LZ77_and_LZ78 LZ77 and LZ78] compression algorithms, Wikipedia
* [https://patents.google.com/patent/US4814746A/en?oq=4814746 Data compression method] for TERSE, patents.google.com
* [http://fileformats.archiveteam.org/wiki/ZIP ZIP archive file format], archiveteam.org, mentions TERSE.
* [https://hercules-390.yahoogroups.narkive.com/gYwJ3QUu/terse-for-pcs-windows-aix-linux terse for PCs (Windows, AIX, Linux ....)], hercules-390@yahoogroups.com
* [https://bit.listserv.ibm-main.narkive.com/82nDDwrh/trsmain-question TRSMAIN question], IBM-Main mailing list
* [https://share.confex.com/share/121/webprogram/Handout/Session14242/14242-%20zOS%20Documentation%20Search%20Strategies%20%28Final%20Edition%29.pdf 14242: z/OS Documentation Search Strategies], presentation slides in PDF format

== Footnotes ==
<references />

[[Category: System Internals]]

Template:TerminalThumb

2026-06-05T20:26:06Z

PoC: Another try

User:PoC

2026-06-05T20:25:09Z

PoC: /* Terminal CSS Test */ 'nother test

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|''Program error'' message (CEE9901) is shown in the message line<ref>In fact, the CPF number being used in the ''QMHSNDPM''-call is shown, CEE9901 appears in the second level text.</ref>, message text is only put into the job log
|Message text is put into the spool file log, followed by ''program error'' message (CEE9901)
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|Message is shown in the Message Line, and put into the job log, followed by ''program error'' message with the CPF number being used in the ''QMHSNDPM''-call
|Message is put into the spool file, sev 40, followed by CPC2402: ''Job ended. Cancel message received at command processor.''
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>, and put into the job log
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|colspan="2"|No result
|}

Batch results were checked with <code>sbmjob cmd(call pgm(myqmhsndpm)) job(myqmhsndpm) log(4 0 *seclvl) logclpgm(*yes)
</code>, to force a job log in any case.

== Terminal CSS Test ==
{{TerminalScreen
|align=right
|width=60ch
|1=<nowiki>
System . . . . . : NIBBLER
Subsystem . . . . : QINTER
Bildschirm . . . : KIFS1

Benutzer . . . . . . . . . . . .
Kennwort . . . . . . . . . . . . __________
Programm/Prozedur . . . . . . . . __________
Menü . . . . . . . . . . . . . . __________
Aktuelle Bibliothek . . . . . . . __________

(C) COPYRIGHT IBM CORP. 1980, 1999.
</nowiki>|2=AS/400 Signon screen}}

== Footnotes ==
<references />

MediaWiki:Common.css

2026-06-05T20:23:46Z

PoC: More CSS magic

/* CSS placed here will be applied to all skins */

/* Terminal-style output */

.terminalthumb {
float: right;
clear: right;
margin: 0 0 1em 1em;
border: 1px solid #a2a9b1;
background: #f8f9fa;
padding: 3px;
width: fit-content;
max-width: 100%;
}

.terminalscreen {
background: #000;
border: 1px solid #444;
color: #00ff00;
font-family: monospace;
min-height: 24em;
overflow: auto;
padding: 1em;
white-space: pre;
width: 80ch;
}

.terminalthumb-right {
float: right;
margin: 0 0 1em 1em;
}

.terminalthumb-left {
float: left;
margin: 0 1em 1em 0;
}

.terminalthumb-center {
float: none;
margin: 1em auto;
}

.terminalcaption {
padding: 0.3em 0.1em 0;
font-size: 88%;
color: #202122;
}

Template:TerminalThumb

2026-06-05T20:22:55Z

PoC: More thumbing

User:PoC

2026-06-05T14:52:29Z

PoC: /* Terminal CSS Test */ Thumb?

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|''Program error'' message (CEE9901) is shown in the message line<ref>In fact, the CPF number being used in the ''QMHSNDPM''-call is shown, CEE9901 appears in the second level text.</ref>, message text is only put into the job log
|Message text is put into the spool file log, followed by ''program error'' message (CEE9901)
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|Message is shown in the Message Line, and put into the job log, followed by ''program error'' message with the CPF number being used in the ''QMHSNDPM''-call
|Message is put into the spool file, sev 40, followed by CPC2402: ''Job ended. Cancel message received at command processor.''
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>, and put into the job log
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|colspan="2"|No result
|}

Batch results were checked with <code>sbmjob cmd(call pgm(myqmhsndpm)) job(myqmhsndpm) log(4 0 *seclvl) logclpgm(*yes)
</code>, to force a job log in any case.

== Terminal CSS Test ==
{{TerminalThumb|<nowiki>
System . . . . . : NIBBLER
Subsystem . . . . : QINTER
Bildschirm . . . : KIFS1

Benutzer . . . . . . . . . . . .
Kennwort . . . . . . . . . . . . __________
Programm/Prozedur . . . . . . . . __________
Menü . . . . . . . . . . . . . . __________
Aktuelle Bibliothek . . . . . . . __________

(C) COPYRIGHT IBM CORP. 1980, 1999.
</nowiki>|AS/400 Signon screen}}

== Footnotes ==
<references />

User:PoC

2026-06-05T14:51:04Z

PoC: /* Terminal CSS Test */ AS/400-Look

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|''Program error'' message (CEE9901) is shown in the message line<ref>In fact, the CPF number being used in the ''QMHSNDPM''-call is shown, CEE9901 appears in the second level text.</ref>, message text is only put into the job log
|Message text is put into the spool file log, followed by ''program error'' message (CEE9901)
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|Message is shown in the Message Line, and put into the job log, followed by ''program error'' message with the CPF number being used in the ''QMHSNDPM''-call
|Message is put into the spool file, sev 40, followed by CPC2402: ''Job ended. Cancel message received at command processor.''
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>, and put into the job log
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|colspan="2"|No result
|}

Batch results were checked with <code>sbmjob cmd(call pgm(myqmhsndpm)) job(myqmhsndpm) log(4 0 *seclvl) logclpgm(*yes)
</code>, to force a job log in any case.

== Terminal CSS Test ==
{{TerminalScreen|<nowiki>
System . . . . . : NIBBLER
Subsystem . . . . : QINTER
Bildschirm . . . : KIFS1

Benutzer . . . . . . . . . . . .
Kennwort . . . . . . . . . . . . __________
Programm/Prozedur . . . . . . . . __________
Menü . . . . . . . . . . . . . . __________
Aktuelle Bibliothek . . . . . . . __________

(C) COPYRIGHT IBM CORP. 1980, 1999.
</nowiki>|AS/400 Signon screen}}

== Footnotes ==
<references />

Template:TerminalThumb

2026-06-05T14:50:16Z

PoC: New

MediaWiki:Common.css

2026-06-05T14:48:26Z

PoC: Expansion

/* CSS placed here will be applied to all skins */

/* Terminal-style output */

.terminalthumb {
float: right;
clear: right;
margin: 0 0 1em 1em;
border: 1px solid #a2a9b1;
background: #f8f9fa;
padding: 3px;
width: fit-content;
max-width: 100%;
}

.terminalscreen {
background: #000;
border: 1px solid #444;
color: #00ff00;
font-family: monospace;
min-height: 24em;
overflow: auto;
padding: 1em;
white-space: pre;
width: 80ch;
}

.terminalcaption {
padding: 0.3em 0.1em 0;
font-size: 88%;
color: #202122;
}

Template:TerminalScreen

2026-06-04T13:04:16Z

PoC: Undo revision 1746 by PoC (talk) Use div

Template:TerminalScreen

2026-06-04T13:02:21Z

PoC: Test

Expanded? {{{1}}}

Template:TerminalScreen

2026-06-04T13:02:00Z

PoC: Undo revision 1744 by PoC (talk)

Template:TerminalScreen

2026-06-04T13:01:38Z

PoC: Test

Template:TerminalScreen

2026-06-04T13:00:29Z

PoC: Undo revision 1742 by PoC (talk)

Template:TerminalScreen

2026-06-04T12:59:40Z

PoC: Test

Parameter: {{{1}}}

User:PoC

2026-06-04T12:58:59Z

PoC: /* Terminal CSS Test */ save

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|''Program error'' message (CEE9901) is shown in the message line<ref>In fact, the CPF number being used in the ''QMHSNDPM''-call is shown, CEE9901 appears in the second level text.</ref>, message text is only put into the job log
|Message text is put into the spool file log, followed by ''program error'' message (CEE9901)
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|Message is shown in the Message Line, and put into the job log, followed by ''program error'' message with the CPF number being used in the ''QMHSNDPM''-call
|Message is put into the spool file, sev 40, followed by CPC2402: ''Job ended. Cancel message received at command processor.''
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>, and put into the job log
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|colspan="2"|No result
|}

Batch results were checked with <code>sbmjob cmd(call pgm(myqmhsndpm)) job(myqmhsndpm) log(4 0 *seclvl) logclpgm(*yes)
</code>, to force a job log in any case.

== Terminal CSS Test ==
{{TerminalScreen|<nowiki>
[root@host ~]# zpool status
pool: tank
state: ONLINE
</nowiki>}}

== Footnotes ==
<references />

Template:TerminalScreen

2026-06-04T12:48:24Z

PoC: Wrap

User:PoC

2026-06-04T12:46:34Z

PoC: /* Terminal CSS Test */

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|''Program error'' message (CEE9901) is shown in the message line<ref>In fact, the CPF number being used in the ''QMHSNDPM''-call is shown, CEE9901 appears in the second level text.</ref>, message text is only put into the job log
|Message text is put into the spool file log, followed by ''program error'' message (CEE9901)
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|Message is shown in the Message Line, and put into the job log, followed by ''program error'' message with the CPF number being used in the ''QMHSNDPM''-call
|Message is put into the spool file, sev 40, followed by CPC2402: ''Job ended. Cancel message received at command processor.''
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>, and put into the job log
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|colspan="2"|No result
|}

Batch results were checked with <code>sbmjob cmd(call pgm(myqmhsndpm)) job(myqmhsndpm) log(4 0 *seclvl) logclpgm(*yes)
</code>, to force a job log in any case.

== Terminal CSS Test ==
{{TerminalScreen|<nowiki>
[root@host ~]# zpool status
pool: tank
state: ONLINE
</nowiki>
}}

== Footnotes ==
<references />

Template:TerminalScreen

2026-06-04T12:44:35Z

PoC: PoC moved page Template:Terminal to Template:TerminalScreen without leaving a redirect

Template:TerminalScreen

2026-06-04T12:44:10Z

PoC: renamed class

MediaWiki:Common.css

2026-06-04T12:43:50Z

PoC: reduce to monochrome

/* CSS placed here will be applied to all skins */

/* Terminal-style output */

.terminalscreen {
background: #000;
border: 1px solid #444;
color: #00ff00;
font-family: monospace;
min-height: 24em;
overflow: auto;
padding: 1em;
white-space: pre;
width: 80ch;
}

User:PoC

2026-06-04T12:42:06Z

PoC: Test

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|''Program error'' message (CEE9901) is shown in the message line<ref>In fact, the CPF number being used in the ''QMHSNDPM''-call is shown, CEE9901 appears in the second level text.</ref>, message text is only put into the job log
|Message text is put into the spool file log, followed by ''program error'' message (CEE9901)
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|Message is shown in the Message Line, and put into the job log, followed by ''program error'' message with the CPF number being used in the ''QMHSNDPM''-call
|Message is put into the spool file, sev 40, followed by CPC2402: ''Job ended. Cancel message received at command processor.''
|-
|valign="top"|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="5"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>, and put into the job log
|-
|valign="top"|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|valign="top"|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|-
|valign="top"|'''<tt>*ESCAPE</tt>'''
|colspan="2"|No result
|}

Batch results were checked with <code>sbmjob cmd(call pgm(myqmhsndpm)) job(myqmhsndpm) log(4 0 *seclvl) logclpgm(*yes)
</code>, to force a job log in any case.

== Terminal CSS Test ==
{{Terminal|<nowiki>
[root@host ~]# zpool status
pool: tank
state: ONLINE
</nowiki>
}}

== Footnotes ==
<references />

Template:TerminalScreen

2026-06-04T12:41:55Z

PoC: Try

Template:TerminalScreen

2026-06-04T12:41:07Z

PoC: There need to be three

Template:TerminalScreen

2026-06-04T12:39:53Z

PoC: Typo

Template:TerminalScreen

2026-06-04T12:38:15Z

PoC: Typo

MediaWiki:Common.css

2026-06-04T12:36:04Z

PoC: +border

/* CSS placed here will be applied to all skins */

/* Terminal-style output */

.terminal {
background: #000;
border: 1px solid #444;
color: #00ff00;
font-family: monospace;
min-height: 24em;
overflow: auto;
padding: 1em;
white-space: pre;
width: 80ch;
}

.terminal-red {
color: #ff6060;
}

.terminal-yellow {
color: #ffff60;
}

.terminal-blue {
color: #80c0ff;
}

Template:TerminalScreen

2026-06-04T12:34:24Z

PoC: Updated

Template:TerminalScreen

2026-06-04T12:29:31Z

PoC: Reintroduce terminal

MediaWiki:Common.css

2026-06-04T12:23:35Z

PoC: 80x24

/* CSS placed here will be applied to all skins */

/* Terminal-style output */

.terminal {
background: #000;
color: #00ff00;
font-family: monospace;
width: 80ch;
min-height: 24em;
white-space: pre;
overflow: auto;
padding: 1em;
}

.terminal-red {
color: #ff6060;
}

.terminal-yellow {
color: #ffff60;
}

.terminal-blue {
color: #80c0ff;
}

MediaWiki:Common.css

2026-06-04T12:20:17Z

PoC: Terminal screen

/* CSS placed here will be applied to all skins */

/* Terminal-style output */

.terminal {
background: #000;
color: #d0d0d0;
font-family: Consolas, Monaco, "Courier New", monospace;
font-size: 14px;
line-height: 1.2;
padding: 1em;
border: 1px solid #444;
border-radius: 4px;
overflow-x: auto;
white-space: pre;
}

.terminal-green {
color: #00ff00;
}

.terminal-red {
color: #ff6060;
}

.terminal-yellow {
color: #ffff60;
}

.terminal-blue {
color: #80c0ff;
}

Wrkprb needs long time to start

2026-05-21T22:14:33Z

PoC: rework: Does not work

Over time, it might become apparent that '''Wrkprb needs longer time to start''', especially if the problem handling facility was used heavily on a slow machine.<ref>Like a 9401-150.</ref>

__TOC__

== Problem description ==
This stems from the fact that the used database files grow indefinitely, because they were created with the flag ''REUSEDLT'' disabled. That means, deleted records stay forever, but cannot be accessed. In my case, the PF had 36 KiB, and the accompanying LF 24 KiB. This is laughably small.

So it's not clear why the command experiences gradual slowdown over time.

== Footnotes ==
<references />

[[Category: System Administration‏‎]]

Porting C-Source to OS/400

2026-05-17T19:05:17Z

PoC: /* Weblinks */ more precise

{{FIXME|Complete with Links to all necessary Books.}}
Because of the ''uncommon'' file handling, name length and character constraints, porting is already a mostly manual task.<ref>It's possible to use stream files in IFS as compiler input, but compiled objects have to be put into a ''QSYS.LIB'', library. So, the file name restrictions apply anyway. The line length problem is mostly gone, though.</ref>

Most often, the real challenge is to manually put together a ''config.h'' file. Since there's no capable UNIX shell environment, <code>./configure</code> is no option.<ref>With V4R5, IBM claims to have implemented the C90 standard in Compiler and C-Library. I did not yet find a readymade ''config.h'' with all statements needed for a C90 environment.</ref>

These are definitions for integers, being used often. This can be put e. g. into a separate header file:
<syntaxhighlight lang="c">
#ifndef __stdint_h
typedef unsigned long long int uint64_t;
typedef unsigned int uint32_t;
typedef unsigned short int uint16_t;
typedef unsigned char uint8_t;
typedef long long int int64_t;
typedef int int32_t;
typedef short int int16_t;
typedef char int8_t;
#define __stdint_h 1
#endif
</syntaxhighlight>
<blockquote>'''Note:''' The IMPI (CISC) C compiler in V3R2 and earlier doesn't know <tt>long long</tt>, it's 32 bits only.</blockquote>

== Preparations for QSYS.LIB ==
Preparations are mostly done on UNIX/Linux side. This is required to make the older V4R5 compiler happy. Newer compilers might be more forgiving.

# Convert to native line endings for your platform, if the source files don't match.
# Convert Tabs to spaces:<ref>Tabs appear in SEU as only one blank. This makes source indentation hardly visible.</ref><br><code>for FILE in *.c *.h; do cp ${FILE} ${FILE}~; expand -i -t4 < ${FILE}~ > ${FILE}; done</code>
# Find out longest line in all C- and H-Files.<br><code>wc -L *.c |sort -rn |head</code>
# Eliminate too long lines by wrapping. This is easily done with <code>set colorcolumn=80</code> in ''vim'', and scrolling through the files with a wide window. <ref>Wider than 80 chars, that is.</ref>
# Find C++-style comments and convert to proper C comments.
# Find function definitions which should be inlined, remove the word "inline" from the definition, and add a hint for the preprocessor/compiler that a function should be inlined before the function definition: <code>#pragma inline (''functionname'')</code>
# Find and remove text following <code>#endif</code> preprocessor statements in the same line (thought as comment).
# Create (at least) '''two''' appropriate SRCPF with matching maximum line lengths through the RCDLEN parameter for CRTSRCPF:
## One (or more) for C-Files (''may'' be named ''QCSRC''),<ref>It could be clever to create one PF per subdirectory.</ref>
## One for H-Files ('''must''' be named ''H'').
# Upload.
## If the file names are already shorter than 10 Characters (excluding file extension), just upload to a SRC PF:<br><code>for FILE in *.c; do echo -n "put ${FILE} MYLIB/QCSRC."; basename ${FILE} .c; done |ftp as400</code><ref>Automatic login and switching to ASCII mode is done though a ''~/.netrc''-file.</ref><ref>FTP ASCII takes care to convert ASCII to EBCDIC.</ref>.
## If the file names are longer, you'll have considerable fun to come up with shorter names. Possibly ''grep'' through, and replace names in all text files if you needed to shorten a ''.h'' name. Finally, put together a text file with appropriate ''put'' commands, and hope for the best.
# Change file type to ''C'':<br><code>for FILE in *.c; do echo "quote rcmd CHGPFM FILE(MYLIB/QCSRC) MBR($(basename ${FILE} .c)) SRCTYPE(C)"; done |ftp as400</code><ref>This is a good example how to exploit the ftp server's ability to call CL commands as a replacement for ''rcmd''.</ref> Note: You'll need to do this for header files, also!

The precompiler searches private includes in ''*LIBL/H'', without the ''.h''-Extension.

== Compile Cycle ==
Compile object files as follows:
CRTCMOD MODULE(MYLIB/MAIN) SRCFILE(MYLIB/QCSRC) DEFINE(DEF1 DEF2=1) OPTION(*LOGMSG) OUTPUT(*PRINT)
* Add <code>SYSIFCOPT(*IFSIO *IFS64IO)</code> to the compiler parameters if the code contains <code>fopen()</code> calls.
* If you added <code>#pragma inline (''functionname'')</code> to the code, add <code>INLINE(*ON)</code> to the compiler parameters

If compilation fails, output will go into a spooled file in the configured output queue. This is the most tedious task.
# Compile,
# check output,
# fix problems,
# <code>goto 1</code>.

If all object modules have been created, you can then link them to a ''*PGM'' object as follows:
CRTPGM PGM(MYLIB/MYPG) MODULE(MYLIB/*ALL) ENTMOD(*PGM) ACTGRP(*NEW) DETAIL(*BASIC)

== Weblinks ==
* [https://github.com/greenfive/as400_c/ AS/400 C] programming related files, especially ''stdint.h'', GitHub

== Footnotes ==
<references />

[[Category:Programming]]

Porting C-Source to OS/400

2026-05-17T19:04:55Z

PoC: +link

{{FIXME|Complete with Links to all necessary Books.}}
Because of the ''uncommon'' file handling, name length and character constraints, porting is already a mostly manual task.<ref>It's possible to use stream files in IFS as compiler input, but compiled objects have to be put into a ''QSYS.LIB'', library. So, the file name restrictions apply anyway. The line length problem is mostly gone, though.</ref>

Most often, the real challenge is to manually put together a ''config.h'' file. Since there's no capable UNIX shell environment, <code>./configure</code> is no option.<ref>With V4R5, IBM claims to have implemented the C90 standard in Compiler and C-Library. I did not yet find a readymade ''config.h'' with all statements needed for a C90 environment.</ref>

These are definitions for integers, being used often. This can be put e. g. into a separate header file:
<syntaxhighlight lang="c">
#ifndef __stdint_h
typedef unsigned long long int uint64_t;
typedef unsigned int uint32_t;
typedef unsigned short int uint16_t;
typedef unsigned char uint8_t;
typedef long long int int64_t;
typedef int int32_t;
typedef short int int16_t;
typedef char int8_t;
#define __stdint_h 1
#endif
</syntaxhighlight>
<blockquote>'''Note:''' The IMPI (CISC) C compiler in V3R2 and earlier doesn't know <tt>long long</tt>, it's 32 bits only.</blockquote>

== Preparations for QSYS.LIB ==
Preparations are mostly done on UNIX/Linux side. This is required to make the older V4R5 compiler happy. Newer compilers might be more forgiving.

# Convert to native line endings for your platform, if the source files don't match.
# Convert Tabs to spaces:<ref>Tabs appear in SEU as only one blank. This makes source indentation hardly visible.</ref><br><code>for FILE in *.c *.h; do cp ${FILE} ${FILE}~; expand -i -t4 < ${FILE}~ > ${FILE}; done</code>
# Find out longest line in all C- and H-Files.<br><code>wc -L *.c |sort -rn |head</code>
# Eliminate too long lines by wrapping. This is easily done with <code>set colorcolumn=80</code> in ''vim'', and scrolling through the files with a wide window. <ref>Wider than 80 chars, that is.</ref>
# Find C++-style comments and convert to proper C comments.
# Find function definitions which should be inlined, remove the word "inline" from the definition, and add a hint for the preprocessor/compiler that a function should be inlined before the function definition: <code>#pragma inline (''functionname'')</code>
# Find and remove text following <code>#endif</code> preprocessor statements in the same line (thought as comment).
# Create (at least) '''two''' appropriate SRCPF with matching maximum line lengths through the RCDLEN parameter for CRTSRCPF:
## One (or more) for C-Files (''may'' be named ''QCSRC''),<ref>It could be clever to create one PF per subdirectory.</ref>
## One for H-Files ('''must''' be named ''H'').
# Upload.
## If the file names are already shorter than 10 Characters (excluding file extension), just upload to a SRC PF:<br><code>for FILE in *.c; do echo -n "put ${FILE} MYLIB/QCSRC."; basename ${FILE} .c; done |ftp as400</code><ref>Automatic login and switching to ASCII mode is done though a ''~/.netrc''-file.</ref><ref>FTP ASCII takes care to convert ASCII to EBCDIC.</ref>.
## If the file names are longer, you'll have considerable fun to come up with shorter names. Possibly ''grep'' through, and replace names in all text files if you needed to shorten a ''.h'' name. Finally, put together a text file with appropriate ''put'' commands, and hope for the best.
# Change file type to ''C'':<br><code>for FILE in *.c; do echo "quote rcmd CHGPFM FILE(MYLIB/QCSRC) MBR($(basename ${FILE} .c)) SRCTYPE(C)"; done |ftp as400</code><ref>This is a good example how to exploit the ftp server's ability to call CL commands as a replacement for ''rcmd''.</ref> Note: You'll need to do this for header files, also!

The precompiler searches private includes in ''*LIBL/H'', without the ''.h''-Extension.

== Compile Cycle ==
Compile object files as follows:
CRTCMOD MODULE(MYLIB/MAIN) SRCFILE(MYLIB/QCSRC) DEFINE(DEF1 DEF2=1) OPTION(*LOGMSG) OUTPUT(*PRINT)
* Add <code>SYSIFCOPT(*IFSIO *IFS64IO)</code> to the compiler parameters if the code contains <code>fopen()</code> calls.
* If you added <code>#pragma inline (''functionname'')</code> to the code, add <code>INLINE(*ON)</code> to the compiler parameters

If compilation fails, output will go into a spooled file in the configured output queue. This is the most tedious task.
# Compile,
# check output,
# fix problems,
# <code>goto 1</code>.

If all object modules have been created, you can then link them to a ''*PGM'' object as follows:
CRTPGM PGM(MYLIB/MYPG) MODULE(MYLIB/*ALL) ENTMOD(*PGM) ACTGRP(*NEW) DETAIL(*BASIC)

== Weblinks ==
* [https://github.com/greenfive/as400_c/ AS/400 C] programming related files, especially ''stdint.h''

== Footnotes ==
<references />

[[Category:Programming]]

Porting C-Source to OS/400

2026-05-10T23:38:44Z

PoC: More types

{{FIXME|Complete with Links to all necessary Books.}}
Because of the ''uncommon'' file handling, name length and character constraints, porting is already a mostly manual task.<ref>It's possible to use stream files in IFS as compiler input, but compiled objects have to be put into a ''QSYS.LIB'', library. So, the file name restrictions apply anyway. The line length problem is mostly gone, though.</ref>

Most often, the real challenge is to manually put together a ''config.h'' file. Since there's no capable UNIX shell environment, <code>./configure</code> is no option.<ref>With V4R5, IBM claims to have implemented the C90 standard in Compiler and C-Library. I did not yet find a readymade ''config.h'' with all statements needed for a C90 environment.</ref>

These are definitions for integers, being used often. This can be put e. g. into a separate header file:
<syntaxhighlight lang="c">
#ifndef __stdint_h
typedef unsigned long long int uint64_t;
typedef unsigned int uint32_t;
typedef unsigned short int uint16_t;
typedef unsigned char uint8_t;
typedef long long int int64_t;
typedef int int32_t;
typedef short int int16_t;
typedef char int8_t;
#define __stdint_h 1
#endif
</syntaxhighlight>
<blockquote>'''Note:''' The IMPI (CISC) C compiler in V3R2 and earlier doesn't know <tt>long long</tt>, it's 32 bits only.</blockquote>

== Preparations for QSYS.LIB ==
Preparations are mostly done on UNIX/Linux side. This is required to make the older V4R5 compiler happy. Newer compilers might be more forgiving.

# Convert to native line endings for your platform, if the source files don't match.
# Convert Tabs to spaces:<ref>Tabs appear in SEU as only one blank. This makes source indentation hardly visible.</ref><br><code>for FILE in *.c *.h; do cp ${FILE} ${FILE}~; expand -i -t4 < ${FILE}~ > ${FILE}; done</code>
# Find out longest line in all C- and H-Files.<br><code>wc -L *.c |sort -rn |head</code>
# Eliminate too long lines by wrapping. This is easily done with <code>set colorcolumn=80</code> in ''vim'', and scrolling through the files with a wide window. <ref>Wider than 80 chars, that is.</ref>
# Find C++-style comments and convert to proper C comments.
# Find function definitions which should be inlined, remove the word "inline" from the definition, and add a hint for the preprocessor/compiler that a function should be inlined before the function definition: <code>#pragma inline (''functionname'')</code>
# Find and remove text following <code>#endif</code> preprocessor statements in the same line (thought as comment).
# Create (at least) '''two''' appropriate SRCPF with matching maximum line lengths through the RCDLEN parameter for CRTSRCPF:
## One (or more) for C-Files (''may'' be named ''QCSRC''),<ref>It could be clever to create one PF per subdirectory.</ref>
## One for H-Files ('''must''' be named ''H'').
# Upload.
## If the file names are already shorter than 10 Characters (excluding file extension), just upload to a SRC PF:<br><code>for FILE in *.c; do echo -n "put ${FILE} MYLIB/QCSRC."; basename ${FILE} .c; done |ftp as400</code><ref>Automatic login and switching to ASCII mode is done though a ''~/.netrc''-file.</ref><ref>FTP ASCII takes care to convert ASCII to EBCDIC.</ref>.
## If the file names are longer, you'll have considerable fun to come up with shorter names. Possibly ''grep'' through, and replace names in all text files if you needed to shorten a ''.h'' name. Finally, put together a text file with appropriate ''put'' commands, and hope for the best.
# Change file type to ''C'':<br><code>for FILE in *.c; do echo "quote rcmd CHGPFM FILE(MYLIB/QCSRC) MBR($(basename ${FILE} .c)) SRCTYPE(C)"; done |ftp as400</code><ref>This is a good example how to exploit the ftp server's ability to call CL commands as a replacement for ''rcmd''.</ref> Note: You'll need to do this for header files, also!

The precompiler searches private includes in ''*LIBL/H'', without the ''.h''-Extension.

== Compile Cycle ==
Compile object files as follows:
CRTCMOD MODULE(MYLIB/MAIN) SRCFILE(MYLIB/QCSRC) DEFINE(DEF1 DEF2=1) OPTION(*LOGMSG) OUTPUT(*PRINT)
* Add <code>SYSIFCOPT(*IFSIO *IFS64IO)</code> to the compiler parameters if the code contains <code>fopen()</code> calls.
* If you added <code>#pragma inline (''functionname'')</code> to the code, add <code>INLINE(*ON)</code> to the compiler parameters

If compilation fails, output will go into a spooled file in the configured output queue. This is the most tedious task.
# Compile,
# check output,
# fix problems,
# <code>goto 1</code>.

If all object modules have been created, you can then link them to a ''*PGM'' object as follows:
CRTPGM PGM(MYLIB/MYPG) MODULE(MYLIB/*ALL) ENTMOD(*PGM) ACTGRP(*NEW) DETAIL(*BASIC)

== Footnotes ==
<references />

[[Category:Programming]]

User:PoC

2026-05-10T21:45:11Z

PoC: /* Message handling table */ More info

User:PoC

2026-05-10T21:21:09Z

PoC: /* Message handling table */ Expanded with *escape

User:PoC

2026-05-10T20:56:21Z

PoC: /* Message handling table */ typo

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="4"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|'''<tt>*INFO</tt>'''
|-
|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="4"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|'''<tt>*INFO</tt>'''
|-
|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="4"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>
|-
|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|}

== Footnotes ==
<references />

User:PoC

2026-05-10T20:52:52Z

PoC: /* Footnotes */ Added notes

I am the principal maintainer of this Wiki.

== Missing ==
This is a list of things I search for:
* COBOL LPPs for V3R2 in ENU (2924)
* Secondary Language Media German (2929) for V4R5
* The LPP for the IBM Gopher server and 5250 based client (https://es.wikipedia.org/wiki/Gopher)
* The LPPs for DAL (https://en.wikipedia.org/wiki/Data_Access_Language)
* The (non-cumulative) PTFs for OS/400 V2R3, bringing AppleTalk support to OS/400:
<blockquote>
----
Before you configure your Apple Macintosh to connect over AppleTalk, you need to install the following PTFs on the AS/400:

* MF06411
* MF06412
* SF14158
* SF14614
* MF06396
* MF06332

These PTFs will not be shipped in a cumulative package, and we advise that you check for any later PTFS that were released after publication of this book.

Cited from Chapter 8 of ''Using Apple Macintosh with the AS/400'', GG24-4071-00, March 1994.
----</blockquote>

== Unofficial Benchmarks ==
For getting a rough idea about CPU speed, I have a physical table about German ZIP codes, including long distance telephone prefixes, filled with nearly 20,000 records in six fields, summing up to 2.25 MiB of data. From the original source in the internet, there were a lot of duplicate records. Birgitta Hauser came up with a quick and dirty idea how to eliminate these dupes.<ref>She admitted, ''it might be a bit slow''.</ref>

Since the SQL proved to be running really slow, I came up to use it as a benchmark. Of course, it's not 100  fair, because of different OS releases and accompanying improvements in SQL handling. But it gives a rough idea.

The SQL was run from a source PF member as standard batch job (default parameters) on idling machines (no additional work).

{| class="wikitable"
!Machine
!Proc. Feat.
!OS
!Runtime (ca.)
!Comments
|-
|9401-150
|2270
|V4R5
|About 118 hrs.
| 
|-
|9406-S20
|2161
|V4R4
|About 13.5 hrs.
| 
|-
|9406-800
|7408
|V5R2
|About 2 hrs.
| 
|-
|8203-E4A
|5587
|V7R2
|1-2 Minutes
|LPAR with two CPU cores assigned.
|}

----

=== Used files ===
* DDS for the database as follows:
A UNIQUE
A R PLZTBL
A ORT 32A
A LAND 17A
A VORWAHL 6A ALWNULL
A PLZ 5A
A ID 5S 0
A ZUSATZ 30A ALWNULL
A K ID

* SQL for ''RUNSQLSTM'' as follows:
DELETE FROM PLZPF A
WHERE A.ID = (
SELECT MAX(ID) FROM PLZPF
GROUP BY ORT, LAND, VORWAHL, PLZ, ZUSATZ
HAVING COUNT(*) > 1 AND MAX(ID) = A.ID)

* Submit Command for ''RUNSQLSTM'' as follows:
SBMJOB JOB(DLTPLZDUPS) CMD(RUNSQLSTM SRCFILE(PLZ/SOURCES) SRCMBR(DLTDUPS) COMMIT(*NONE) NAMING(*SQL) DFTRDBCOL(PLZ))

I can provide a save file of the whole library on request.

The switchback to the traditional CQE SQL Engine involves creating a copy of ''QSYS/QAQQINI'', updating this copy through SQL, SQE_NATIVE_ACCESS.

=== Weblinks ===
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/createqaqqini.htm Creating a QAQQINI File]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/specifyqaqqini.htm Change Query Attributes for using the desired QAQQINI file]
* [https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/rzajq/rzajqqaqqiniformat.htm QAQQINI File Format]

== Message handling table ==
This is related to the [https://www.ibm.com/docs/en/i/7.4.0?topic=ssw_ibm_i_74/apis/QMHSNDPM.html QMHSNDPM] API.

When trying out these things, it's important to have some calls to <code>sleep()</code> in the application, so the 5250 display logic does not merge away the brief write request.

{|class="wikitable"
!valign="top" rowspan="2"|Type
!valign="top" rowspan="2"|Destination
!colspan="2"|Result
|-
!Interactive
!Batch
|-
|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="4"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter v0'''
|valign="top" rowspan="2"|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|'''<tt>*INFO</tt>'''
|-
|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="4"|'''<tt>*PGMBDY</tt>''',<br>Call Stack Counter '''1'''
|valign="top" rowspan="2"|Message is put into the job log, and shown in the message line
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|'''<tt>*INFO</tt>'''
|-
|'''<tt>*STATUS</tt>'''
|colspan="2"|No result
|-
|'''<tt>*COMP</tt>'''
|Message is put into the job log
|Message is put into the spool file, sev 40
|-
|'''<tt>*DIAG</tt>'''
|valign="top" rowspan="4"|'''<tt>*EXT</tt>'''
|Message is put into the job log
|valign="top" rowspan="2"|Message is put into the spool file, sev 40
|-
|'''<tt>*INFO</tt>'''
|Message is shown in a separate screen, like RPG's <code>DSPLY</code>
|-
|'''<tt>*STATUS</tt>'''
|Message is shown in the Message Line
|No result
|-
|'''<tt>*COMP</tt>'''
|No result
|Message is put into the spool file, sev 40
|}

== Footnotes ==
<references />

Access OS/390 DB2 database tables from OS/400 over SNA/APPN

2026-05-10T18:08:49Z

PoC: /* WTO: Dispatch Priorities not in Sync */ Syntax

{{FIXME|Solve and document outstanding headscratchers}}
This is a short writeup of how to '''access OS/390 DB2 database tables from OS/400 over SNA/APPN'''. A mandatory requirement is an already established SNA/APPN configuration.

__TOC__

This article assumes OS/390 ADCD 2.10 being used.

== Setup OS/390 IPL parameters ==
Change the configuration parameter: <code>LOADPARM 0A822C..</code> and IPL for an initial cold start handler of DB2.

Subsequent IPLs should use <code>LOADPARM 0A822W..</code> to use the quicker warm start facility.

DB2 parameters are left at default, because we don't know (yet) how to change them.

=== Startup summary on OS/390 console ===
This is where I gleaned interesting APPN values.
- 17.05.53 STC00017 DSNL004I - DDF START COMPLETE
- LOCATION S390LOC
- LU P390LU
- GENERICLU -NONE
- DOMAIN -NONE
- TCPPORT 446
- RESPORT 5020
- 17.05.53 STC00017 DSN9022I - DSNYASCP 'START DB2' NORMAL COMPLETION
- 17.05.53 STC00024 +DSNX964I DSNX9STP THE DB2-ESTABLISHED STORED
- PROCEDURES ADDRESS SPACE
- FOR SUBSYSTEM DSN1 IS STARTED

* S390LOC is (also) the default database name,
* P390LU is the network entity (LUname) name we must connect to.

==== WTO: Dispatch Priorities not in Sync ====
In the default installation of OS/390 2.10 ADCD, you might be presented with this console message:
*17.05.41 STC00017 *DSNT405E - DSNTLIDE DISPATCH PRIORITIES NOT IN SYNC:
* IRLM : 0020 COMPARED TO DB2 : 0021

The following edits need to be made:
* to <tt>sys1.adcd10.parmlib(ieaics00)</tt>, insert the following lines before the ''SUBSYS=CICS'' line:
TRXNAME=DB2,PGN=12 /* DB2 */
TRXNAME=DSN1MSTR,PGN=12
TRXNAME=DSN1DIST,PGN=12
TRXNAME=DSN1SPAS,PGN=12
TRXNAME=DB2IRLM,PGN=13

* to sys1.adcd10.parmlib(ieaips00) insert the following lines after the ''PGN=3,'' line:
PGN=12,(DMN=5,DP=F2) /* DB2 */
PGN=13,(DMN=5,DP=F4) /* DB2 IRLM */

Re-IPL, and the message will be gone.

== Use interactive SQL ==
To get ISPF menus related to DB, use <code>DBSPROC</code> instead of default <code>ISPFPROC</code> as logon proc at logon time.

The interactive SQL facility can be reached:
* Type <code>M.15</code> from the ISPF main menu,
* Type <code>2.1</code> in the subsequent *DB2 Administration Menu*.

Unfortunately, this can't be done in one go.

Below the ''SQL statement:'' line on the appearing screen, SQL commands can be entered. Example:
* <code>CREATE DATABASE foobar</code>
* <code>CREATE TABLE foobar.testtbl (id char(24))</code>
* <code>INSERT INTO foobar.testtbl VALUES ('barbaz')</code>
* <code>SELECT * FROM foobar.testtbl</code>

== Retrieving information about available databases ==
The tool is named DB2I. You can reach it from ISPF main menu:
* Type <code>M.13</code> in ISPF,
* Type <code>D</code> into the the subsequent ''DB2I PRIMARY OPTION MENU'''s command line,
* Change <code>DB2 NAME</code> to be ''DSN1'',
* Press <code>Enter</code> twice,
* Type <code>7</code> in the subsequent ''DB2I PRIMARY OPTION MENU'',
* Choose any predefined ''Cmd x'' line, and enter:
-DISPLAY DATABASE(*) LIMIT(1000)
* Adjust ''LIMIT'' as needed,
* Press <code>Enter</code> to see a list of defined databases.

Output shows ''NO SPACES FOUND'' for our database from above. Do we need to create/assign separate table space first?

== Remote connection from OS/400 ==
To access remote databases, an according entry in the remote database directory needs to be created.
addrdbdire rdb(s390loc) rmtlocname(p390lu *sna) dev(p390lu) lcllocname(*netatr) rmtnetid(*netatr) mode(ibmrdb) text('Default DB2 instance on OS/390 ADCD')
OS/400 creates an according device description upon the first connection request.

From <code>strsql</code>, a remote connection can now be initiated:
CONNECT TO S390LOC USER P390 USING 'P390'

<blockquote>'''Note:''' Use your actual password for the P390 user.</blockquote>

From the SQL prompt you can then issue the usual SQL commands, such as ''SELECT''ing the record inserted above:
SELECT * FROM foobar.testtbl

== Further clarifications needed ==
* After inserting records from OS/400, and ''SELECT''ing them in OS/390, the session hangs. A small window appears at bottom, stating <code>SQL cost=2</code>. Pressing <code>PA1</code> ends the session with the interactive SQL facility but doesn't resolve the issue.
** Apparently ''SQL cost'' is an estimate for the database management but not an actual error. Many operations in the DB2 Admin application seem to just hang until an eventual timeout with respective WTO output and messages on screen.
* Which parameters are needed for <code>crtddmf</code> on OS/400 to access remote DB2 tables? Example (not working, need to clarify about possible <code>'P390.DATABASE.FILE'</code>):
crtddmf file(qgpl/p390db) rmtfile(*nonstd 'P390.DATABASE.FILE') rmtlocname(p390lu) dev(p390lu) lcllocname(*netatr) mode(ibmrdb) rmtnetid(*netatr)
** Further research indicates that there might not be a counterpart for DDM access in DB2, but a ''Distributed FileManager/MVS'' component for accessing files at the data set level.
* ''NO SPACES FOUND'', see above. Possible clues:
** [https://www.ibm.com/docs/en/db2-for-zos/12?topic=messages-dsnt602i DSNT602I NO SPACES FOUND], Db2 for z/OS, IBM
** [http://www.ustools.sys.eds.com/usercomms/view.php?bn=usercommunications_interactives&key=1444666587 Usercomm - DB2 V10 Hold Data and Cover Letters for HP Release level AI00], search for ''UI22580 COVER LETTER START''.

== Weblinks ==
* [https://github.com/SDL-Hercules-390/hyperion/blob/master/readme/README.SNA.md Hercules SNA support README], GitHub
* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=SG24620400 S/390 Partners in Development: OS/390 (and z/OS) New Users Cookbook], SG24-6204-00
* [https://www.youtube.com/watch?v=D427APErjcc Mainframe DB2] (YouTube video) by racingmars

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

Access OS/390 DB2 database tables from OS/400 over SNA/APPN

2026-05-08T20:00:45Z

PoC: /* Startup summary on OS/390 console */ mishap

{{FIXME|Solve and document outstanding headscratchers}}
This is a short writeup of how to '''access OS/390 DB2 database tables from OS/400 over SNA/APPN'''. A mandatory requirement is an already established SNA/APPN configuration.

__TOC__

This article assumes OS/390 ADCD 2.10 being used.

== Setup OS/390 IPL parameters ==
Change the configuration parameter: <code>LOADPARM 0A822C..</code> and IPL for an initial cold start handler of DB2.

Subsequent IPLs should use <code>LOADPARM 0A822W..</code> to use the quicker warm start facility.

DB2 parameters are left at default, because we don't know (yet) how to change them.

=== Startup summary on OS/390 console ===
This is where I gleaned interesting APPN values.
- 17.05.53 STC00017 DSNL004I - DDF START COMPLETE
- LOCATION S390LOC
- LU P390LU
- GENERICLU -NONE
- DOMAIN -NONE
- TCPPORT 446
- RESPORT 5020
- 17.05.53 STC00017 DSN9022I - DSNYASCP 'START DB2' NORMAL COMPLETION
- 17.05.53 STC00024 +DSNX964I DSNX9STP THE DB2-ESTABLISHED STORED
- PROCEDURES ADDRESS SPACE
- FOR SUBSYSTEM DSN1 IS STARTED

* S390LOC is (also) the default database name,
* P390LU is the network entity (LUname) name we must connect to.

==== WTO: Dispatch Priorities not in Sync ====
In the default installation of OS/390 2.10 ADCD, you might be presented with this console message:
*17.05.41 STC00017 *DSNT405E - DSNTLIDE DISPATCH PRIORITIES NOT IN SYNC:
* IRLM : 0020 COMPARED TO DB2 : 0021

The following edits need to be made.

* to <tt>sys1.adcd10.parmlib(ieaics00)</tt>, insert the following lines before the ''SUBSYS=CICS'' line:
TRXNAME=DB2,PGN=12 /* DB2 */
TRXNAME=DSN1MSTR,PGN=12
TRXNAME=DSN1DIST,PGN=12
TRXNAME=DSN1SPAS,PGN=12
TRXNAME=DB2IRLM,PGN=13

* to sys1.adcd10.parmlib(ieaips00) insert the following lines after the ''PGN=3,'' line:
PGN=12,(DMN=5,DP=F2) /* DB2 */
PGN=13,(DMN=5,DP=F4) /* DB2 IRLM */

Re-IPL, and the message will be gone.

== Use interactive SQL ==
To get ISPF menus related to DB, use <code>DBSPROC</code> instead of default <code>ISPFPROC</code> as logon proc at logon time.

The interactive SQL facility can be reached:
* Type <code>M.15</code> from the ISPF main menu,
* Type <code>2.1</code> in the subsequent *DB2 Administration Menu*.

Unfortunately, this can't be done in one go.

Below the ''SQL statement:'' line on the appearing screen, SQL commands can be entered. Example:
* <code>CREATE DATABASE foobar</code>
* <code>CREATE TABLE foobar.testtbl (id char(24))</code>
* <code>INSERT INTO foobar.testtbl VALUES ('barbaz')</code>
* <code>SELECT * FROM foobar.testtbl</code>

== Retrieving information about available databases ==
The tool is named DB2I. You can reach it from ISPF main menu:
* Type <code>M.13</code> in ISPF,
* Type <code>D</code> into the the subsequent ''DB2I PRIMARY OPTION MENU'''s command line,
* Change <code>DB2 NAME</code> to be ''DSN1'',
* Press <code>Enter</code> twice,
* Type <code>7</code> in the subsequent ''DB2I PRIMARY OPTION MENU'',
* Choose any predefined ''Cmd x'' line, and enter:
-DISPLAY DATABASE(*) LIMIT(1000)
* Adjust ''LIMIT'' as needed,
* Press <code>Enter</code> to see a list of defined databases.

Output shows ''NO SPACES FOUND'' for our database from above. Do we need to create/assign separate table space first?

== Remote connection from OS/400 ==
To access remote databases, an according entry in the remote database directory needs to be created.
addrdbdire rdb(s390loc) rmtlocname(p390lu *sna) dev(p390lu) lcllocname(*netatr) rmtnetid(*netatr) mode(ibmrdb) text('Default DB2 instance on OS/390 ADCD')
OS/400 creates an according device description upon the first connection request.

From <code>strsql</code>, a remote connection can now be initiated:
CONNECT TO S390LOC USER P390 USING 'P390'

<blockquote>'''Note:''' Use your actual password for the P390 user.</blockquote>

From the SQL prompt you can then issue the usual SQL commands, such as ''SELECT''ing the record inserted above:
SELECT * FROM foobar.testtbl

== Further clarifications needed ==
* After inserting records from OS/400, and ''SELECT''ing them in OS/390, the session hangs. A small window appears at bottom, stating <code>SQL cost=2</code>. Pressing <code>PA1</code> ends the session with the interactive SQL facility but doesn't resolve the issue.
** Apparently ''SQL cost'' is an estimate for the database management but not an actual error. Many operations in the DB2 Admin application seem to just hang until an eventual timeout with respective WTO output and messages on screen.
* Which parameters are needed for <code>crtddmf</code> on OS/400 to access remote DB2 tables? Example (not working, need to clarify about possible <code>'P390.DATABASE.FILE'</code>):
crtddmf file(qgpl/p390db) rmtfile(*nonstd 'P390.DATABASE.FILE') rmtlocname(p390lu) dev(p390lu) lcllocname(*netatr) mode(ibmrdb) rmtnetid(*netatr)
** Further research indicates that there might not be a counterpart for DDM access in DB2, but a ''Distributed FileManager/MVS'' component for accessing files at the data set level.
* ''NO SPACES FOUND'', see above. Possible clues:
** [https://www.ibm.com/docs/en/db2-for-zos/12?topic=messages-dsnt602i DSNT602I NO SPACES FOUND], Db2 for z/OS, IBM
** [http://www.ustools.sys.eds.com/usercomms/view.php?bn=usercommunications_interactives&key=1444666587 Usercomm - DB2 V10 Hold Data and Cover Letters for HP Release level AI00], search for ''UI22580 COVER LETTER START''.

== Weblinks ==
* [https://github.com/SDL-Hercules-390/hyperion/blob/master/readme/README.SNA.md Hercules SNA support README], GitHub
* [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=SG24620400 S/390 Partners in Development: OS/390 (and z/OS) New Users Cookbook], SG24-6204-00
* [https://www.youtube.com/watch?v=D427APErjcc Mainframe DB2] (YouTube video) by racingmars

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