Try-AS/400 - Recent changes [en]

ZuluSCSI

PoC — Tue, 22 Sep 2026 19:52:21 GMT

Moved content to GitHub repo

Terminal graphics support

PoC — Fri, 18 Sep 2026 16:25:16 GMT

typo

← Older revision		Revision as of 18:25, 18 September 2026
(One intermediate revision by the same user not shown)
Line 15:		Line 15:
	This is a function of the 5250 controller in tandem with a hardware terminal, or a feature of the emulator itself. It provides automatic replacement of on-screen objects with a more or less graphical representation of an object. This includes, but is not limited to:		This is a function of the 5250 controller in tandem with a hardware terminal, or a feature of the emulator itself. It provides automatic replacement of on-screen objects with a more or less graphical representation of an object. This includes, but is not limited to:
	* Window borders		* Window borders
	* DDS<ref>Should also work with UIM ~~tags~~, but not real life tested.</ref> <code>MLTCHCFLD</code> as check boxes		* DDS<ref>Should also work with UIM panels, but not real life tested.</ref> <code>MLTCHCFLD</code> as check boxes
	* DDS <code>SNGCHCFLD</code> as radio buttons		* DDS <code>SNGCHCFLD</code> as radio buttons
	* DDS <code>SFLEND(*SCRBAR)</code> for load-all subfiles		* DDS <code>SFLEND(*SCRBAR)</code> for load-all subfiles
Line 28:		Line 28:

	== APA ==		== APA ==
	''All Points Addressable'' is IBM lingo for pixel graphics support. Little is known about this mode at all, and its sole use case was the `dspfax` command, to see received Faxes in TIFFG4 format.		''All Points Addressable'' is IBM lingo for pixel graphics support. Little is known about this mode at all, and its sole use case was the <code>dspfax</code> command, to see received Faxes in TIFFG4 format.

	According to documentation, the 3489 is the only hardware terminal supporting this display mode.		According to documentation, the 3489 is the only hardware terminal supporting this display mode.

Terminal graphics support

PoC — Fri, 18 Sep 2026 16:23:29 GMT

New

New page

There are three modes of '''graphics support''' in OS/400 regarding '''terminals'''.

== GDDM ==
A subset of the mainframe ''Graphical Data Display Manager'' was ported to OS/400.

GDDM needs special support regarding terminals. The only existing twinax terminal supporting GDDM was the 5292 model 2.

Emulators supporting GDDM:
* IBM PC support for DOS (not verified), with special drivers, resolutions up to 1024×768 might be possible,
* an older IDEAcomm release for Windows 3.1 (16 bit), precise version not known.

In later times, it was presumably meant as a way to create graphics for printing.

== Enhanced display ==
This is a function of the 5250 controller in tandem with a hardware terminal, or a feature of the emulator itself. It provides automatic replacement of on-screen objects with a more or less graphical representation of an object. This includes, but is not limited to:
* Window borders
* DDS<ref>Should also work with UIM tags, but not real life tested.</ref> <code>MLTCHCFLD</code> as check boxes
* DDS <code>SNGCHCFLD</code> as radio buttons
* DDS <code>SFLEND(*SCRBAR)</code> for load-all subfiles

Enhanced display needs special support regarding terminals. It is present at least in the twinax 3486 terminal, but presumably in all 348x terminals.

Emulators supporting Enhanced Display:
* all (newer?) IBM provided 5250 emulators
** iACS
** Client Access
* tn5250j (seems to be broken)

== APA ==
''All Points Addressable'' is IBM lingo for pixel graphics support. Little is known about this mode at all, and its sole use case was the `dspfax` command, to see received Faxes in TIFFG4 format.

According to documentation, the 3489 is the only hardware terminal supporting this display mode.

No known emulators support APA.

== See also ==
* [[IBM Twinax-Terminals Overview]]
* [[Communications Traces]]

== Weblinks ==
* [https://www.ibm.com/docs/en/i/7.4.0?topic=device-application-display-programming Application Display Programming] (PDF download), IBM.com

== Footnotes ==
<references />

[[Category: History]]
[[Category: System Internals]]

ZuluSCSI

PoC — Thu, 10 Sep 2026 16:10:32 GMT

Tape drive support: missing word

← Older revision		Revision as of 18:10, 10 September 2026
(One intermediate revision by the same user not shown)
Line 89:		Line 89:
	=== Tape drive support ===		=== Tape drive support ===
	Currently, two tape drives are emulated:		Currently, two tape drives are emulated:
	* a CISC era QIC1000, FC #6343,		* <code>Device = "AS400_CISC"</code>, a CISC era QIC1000, FC #6343,
	* a PCI/RISC era SLR5 drive.		* <code>Device = "AS400_PPC"</code>, a PCI/RISC era SLR5 drive.

			To use,
	* create directory <code>TP0</code>,		* create directory <code>TP0</code>,
	* populate with one or more 0 byte files named <code>*.tap</code> files, e. g. by using the Unix <code>touch</code>,		* populate with one or more 0 byte files named <code>*.tap</code> files, e. g. by using the Unix <code>touch</code> command,
	* use the serial console to attach image(s) to the drive.		* use the serial console to attach image(s) to the drive.

			Without any ''Device'' parameter, a standard tape drive is emulated, with no special AS/400 quirks. This works with many PPC/PCI machines. However, the presence of a ''TapeDensity'' parameter seems necessary in ''zuluscsi.ini''.
			[SCSI0]
			TapeDensity = 0x25

			For trying an emulated SLR5 drive:
	* ''zuluscsi.ini'':		* ''zuluscsi.ini'':
	[SCSI0]		[SCSI0]

IBM BOOK format

PoC — Thu, 10 Sep 2026 08:57:47 GMT

Updated page

← Older revision		Revision as of 10:57, 10 September 2026
Line 1:		Line 1:
	~~{{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 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.		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 file-internal style (?) 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.		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 ==		== 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?~~		The internal structure is fully documented as a part of the ''Geist'' reference implementation on GitHub.

	* 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 ==		== See also ==
Line 28:		Line 14:

	== Weblinks ==		== Weblinks ==
			* [https://github.com/cyberdotgent/geist Geist IBM Book format reference implementation]
			** [https://github.com/cyberdotgent/geist/tree/main/doc/boo-spec Geist Book format documentation]
	* [http://www.edm2.com/index.php/BookManager BookManager Releases] contains history of IBM BookManager releases		* [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://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

ZuluSCSI

PoC — Tue, 08 Sep 2026 12:15:29 GMT

Examples: More precise on tapes

← Older revision		Revision as of 14:15, 8 September 2026
Line 88:		Line 88:

	=== Tape drive support ===		=== Tape drive support ===
			Currently, two tape drives are emulated:
			* a CISC era QIC1000, FC #6343,
			* a PCI/RISC era SLR5 drive.

	* create directory <code>TP0</code>,		* create directory <code>TP0</code>,
	* populate with one or more 0 byte files named <code>*.tap</code> files, e. g. by using the Unix <code>touch</code>,		* populate with one or more 0 byte files named <code>*.tap</code> files, e. g. by using the Unix <code>touch</code>,
Line 98:		Line 102:
	* When you choose an image file through the USB port's media menu, make sure that you not only choose an image file, but afterwards ''insert'' it!		* When you choose an image file through the USB port's media menu, make sure that you not only choose an image file, but afterwards ''insert'' it!
	* If you replace a hardware tape drive, make sure to delete your old tape device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.		* If you replace a hardware tape drive, make sure to delete your old tape device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.
	* The amended (with an explicit ''Device'' statement) tape code as of v2026.08.28 has not yet undergone extensive testing.		* The amended (with an explicit ''Device'' statement) tape code as of v2026.08.28 has not yet undergone extensive testing. Initial tests yield mixed results.

	=== CD drive support ===		=== CD drive support ===
Line 111:		Line 115:
	* If you replace a hardware CD drive, make sure to delete your old CD device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.		* If you replace a hardware CD drive, make sure to delete your old CD device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.

	Tested with Firmware 2026-08-07, 9401-150, V4R4, V5R2: IPL only so far, but that works.		Tested with Firmware 2026-08-07, 9401-150, V4R4, V5R2: IPL only so far, but that works. '''Note:''' CISC era OS/400 has no CD-ROM support whatsoever.

	=== Disk drive support ===		=== Disk drive support ===

Panel Usage

PoC — Sun, 06 Sep 2026 19:42:13 GMT

Elements: Amber LED

← Older revision		Revision as of 21:42, 6 September 2026
Line 10:		Line 10:
	* LED (green) for showing the power state,		* LED (green) for showing the power state,
	* LED (green), with a pictogram reminding of stairs (main processor activity),<ref>It is not the disk activity LED as it was usual with PCs was into the 2000s.</ref>		* LED (green), with a pictogram reminding of stairs (main processor activity),<ref>It is not the disk activity LED as it was usual with PCs was into the 2000s.</ref>
	* LED (amber) with a vertical bar, cut in half and one half moved slightly horizontal.		* LED (amber) with a vertical bar, cut in half and one half moved slightly horizontal (error<ref>In other words: System activity is halted and will not try to recover until a reset is issued. Reset means power cycle.</ref>).

	Usually after plugging the power, the LCD will light up green.		Usually after plugging the power, the LCD will light up green.

Post-Install Optimizations

PoC — Thu, 03 Sep 2026 16:23:04 GMT

Security System Values: Typo

← Older revision		Revision as of 18:23, 3 September 2026
Line 103:		Line 103:
	* For TCP connections to work, we need encrypted passwords.		* For TCP connections to work, we need encrypted passwords.
	CHGDDMTCPA PWDRQD(*ENCRYPTED)		CHGDDMTCPA PWDRQD(*ENCRYPTED)
	* Allow ''QSYSOPR'' ~~signon~~ to all devices.		* Allow ''QSYSOPR'' sign-on to all devices.
	CHGSYSVAL SYSVAL(QLMTSECOFR) VALUE('0')		CHGSYSVAL SYSVAL(QLMTSECOFR) VALUE('0')
	* Raise maximum password length to maximum value.<ref>In newer OS versions, an additional variable ''QPWDLVL'' allows even longer passwords.</ref>		* Raise maximum password length to maximum value.<ref>In newer OS versions, an additional variable ''QPWDLVL'' allows even longer passwords.</ref>

User:Aperez

PoC — Sun, 30 Aug 2026 16:37:00 GMT

User account Aperez was created by PoC and password was sent by email

ZuluSCSI

PoC — Sat, 29 Aug 2026 20:59:40 GMT

Tape drive support: Removed inert entry

← Older revision		Revision as of 22:59, 29 August 2026
(6 intermediate revisions by the same user not shown)
Line 8:		Line 8:

	The ZuluSCSI firmware can emulate multiple devices at once. There is no real need to add multiple Zulus to a given SCSI bus. One Zulu can easily saturate even the UltraWide SCSI bus of a 9401-150, and due to the SD card, delays are minimal. You can gain more performance with bigger machines, if they have multiple SCSI buses, though.		The ZuluSCSI firmware can emulate multiple devices at once. There is no real need to add multiple Zulus to a given SCSI bus. One Zulu can easily saturate even the UltraWide SCSI bus of a 9401-150, and due to the SD card, delays are minimal. You can gain more performance with bigger machines, if they have multiple SCSI buses, though.

			<blockquote>'''Note:''' Current state of affairs is that at least for writes, the SD card itself is a considerable brake shoe for writes, presumably because of so called 'Write Amplification''. This is not meant to stay like this forever. Optimizations are possible and will be implemented eventually.</blockquote>

	== Hardware overview ==		== Hardware overview ==
Line 33:		Line 35:
	The firmware presents a simple menu driven UI for some tasks.		The firmware presents a simple menu driven UI for some tasks.

	There is no need to shut down the device itself, it's safe to "pull the plug" when there is no activity. The Operating System running on the attached computer should, though.		There is no need to shut down the device itself, it's safe to "pull the plug" when there is no activity. The Operating System running on the attached computer should be orderly shut down, though.

	== Configuration ==		== Configuration ==
Line 73:		Line 75:

	=== Directories ===		=== Directories ===
	For a device usually allowing dynamic addition and removal of media — CD-ROM-, and tape drives. The naming scheme follows the same structure as files, but ''[any text]'' must be omitted.		For a device usually allowing dynamic addition and removal of media — CD-ROM-, and tape drives, you can create a directory instead of a file. The naming scheme follows the same structure as files, but ''[any text]'' must be omitted.

	Files within the directories can be freely named~~, and are used in alphabetical order~~.~~<ref>Either through the~~ ''Eject'' button~~, or~~ the ~~media~~ menu.~~</ref>~~		Files within the directories can be freely named. The ''Eject'' button loads and inserts the next image in order. Individual images can be inserted through the menu via USB.

	=== Configuration file ===		=== Configuration file ===
Line 90:		Line 92:
	* use the serial console to attach image(s) to the drive.		* use the serial console to attach image(s) to the drive.
	* ''zuluscsi.ini'':		* ''zuluscsi.ini'':
	~~[SCSI]~~
	~~System="AS400_PPC"~~

	[SCSI0]		[SCSI0]
	~~TapeDensity~~ = ~~0x25~~		Device = "AS400_PPC"

	Caveats:		Caveats:
	* When you choose an image file through the USB port's media menu, make sure that you not only choose an image file, but afterwards ''insert'' it!		* When you choose an image file through the USB port's media menu, make sure that you not only choose an image file, but afterwards ''insert'' it!
	* If you replace a hardware tape drive, make sure to delete your old tape device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.		* If you replace a hardware tape drive, make sure to delete your old tape device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.
			* The amended (with an explicit ''Device'' statement) tape code as of v2026.08.28 has not yet undergone extensive testing.
	~~This configuration has been tested over the course~~ of ~~multiple weeks:~~
	* Occasional <tt>go save</tt> 21,
	* daily differential backups,
	* occasional single file restores.

	~~Tested with Firmware 2026-06-12, 9401-150, V4R5~~.

	=== CD drive support ===		=== CD drive support ===
Line 118:		Line 111:
	* If you replace a hardware CD drive, make sure to delete your old CD device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.		* If you replace a hardware CD drive, make sure to delete your old CD device file first, then IPL, check/set the new device name in DST, and have auto-configuration create the new device file during the following IPL.

	Tested with Firmware 2026-08-07, 9401-150, V4R4: IPL only so far.		Tested with Firmware 2026-08-07, 9401-150, V4R4, V5R2: IPL only so far, but that works.

	=== Disk drive support ===		=== Disk drive support ===
	The officially released code base is able to present ~~a singular #6717, 8.5 GiB~~ disk ~~drive~~ to the system, initialize, and install SLIC + base OS/400 + LPPs + PTFs.		The officially released code base is able to present multiple disk drives to the system, initialize, and install SLIC + base OS/400 + LPPs + PTFs.

	* ~~Generate disk image:~~		* Copy ''as400_disk_definitions.txt'' from the official GitHub repository to the SD card.
	~~dd if=/dev/zero~~ of~~=HD6.img bs=522 count=17177940 status=progress~~		** Because of serial numbers currently being hard coded, only one disk per type should be used for now!
	* ''zuluscsi.ini'':		* ''zuluscsi.ini'':
	[SCSI]		[SCSI]
	System = AS400_PPC		System = AS400_PPC

	[SCSI6]		[SCSI6]
			AS400_DiskProfile = "09L4044"
	PrefetchBytes = 0		PrefetchBytes = 0

			When a ''AS400_DiskProfile'' is configured for a given SCSI ID, and the associated image cannot be found on the SD card, a new one is generated automatically, with the correct size. This takes some time, so wait until the activity LED stays unlit.

			There is a shell-script <code>utils/extract_as400_disk_data.sh</code> in the original source tree on GitHub to generate more ''as400_disk_definitions.txt'' entries from real disks connected to a SCSI controller when ran under Linux.

	Caveats:		Caveats:
	* Writes to the emulated disk are very slow compared to reads.		* Writes to the emulated disk are very slow compared to reads.
	* One user with a RP2040 reported failure for the disk to be recognized. Prerelease firmware solved the issue.

	Fully tested with Firmware ~~2026-~~08~~-21~~, 9401-150, V4R4.		Fully tested with Firmware v2026.08.27RC1, 9401-150, V4R4, V5R2.

	== Current state ==		== Current state ==
Line 162:		Line 159:
	\|}		\|}

	All successful tests so far have been based on a ZuluSCSI wide board, while the CISC tests have been done with a ZuluSCSI Blaster.		All successful tests so far have been based on a ZuluSCSI wide board on a 9401-150, while the CISC tests have been done with a ZuluSCSI Blaster on a 9401-P02.

	~~== Next ==~~		There are success reports of more 150's working, and one of a 9406-270 becoming stuck with A6000244, ''Contact was lost with device indicated''.
	~~These features~~ are ~~completed, partially tested, but did not make it to the official releases yet:~~
	* More disk profiles, loadable in ''zuluscsi.ini'' via external file ''as400_disk_definitions.txt'', ~~so different types than the built~~-~~in 522 bytes~~, ~~8.5 GiB #6717 can be assigned.~~
	** Shellscript to generate more ''~~as400_disk_definitions.txt~~'' ~~entries from real disks connected to a SCSI controller when ran under Linux~~
	** Because of serial numbers currently being hard coded, only one disk per type should be used
	* Allowed more memory to accommodate the necessary VPD SCSI pages for multiple disks
	* Present captured real tape VPD/SCSI data from IBM SLR5/QIC1000 when using <code>Device = "AS400_PPC"</code> or <code>Device = "AS400_CISC"</code> in an ID stanza
	* Created a new build profile for the ZuluSCSI Blaster, removing all the add-on code being unneeded when used with AS/400

	== See also ==		== See also ==

Serial networking scenarios with Cisco-Routers

PoC — Tue, 25 Aug 2026 21:17:59 GMT

Configuration: OS/400 (Fiona): Fixed inconsistency

← Older revision		Revision as of 23:17, 25 August 2026
Line 327:		Line 327:
	crtlinx25 lind(x25line) rsrcname(lin011) lglchle((001 pvc)) netadr(00000000000000) cnninit(local) interface(*rs232v24) linespeed(19200) dftpktsize(1024) modulus(128) dftwdwsize(8) linkspeed(64000) cmnrcylmt(10 1)		crtlinx25 lind(x25line) rsrcname(lin011) lglchle((001 pvc)) netadr(00000000000000) cnninit(local) interface(*rs232v24) linespeed(19200) dftpktsize(1024) modulus(128) dftwdwsize(8) linkspeed(64000) cmnrcylmt(10 1)

	crtctlappc ctld(nibbler) linktype(x25) line(x25line) maxframe(1024) rmtcpname(nibbler) exchid(05641700) netlvl(1984) lglchlid(~~006~~) nodetype(calc) tmsgrpnbr(calc) autodltdev(no) cmnrcylmt(10 1)		crtctlappc ctld(nibbler) linktype(x25) line(x25line) maxframe(1024) rmtcpname(nibbler) exchid(05641700) netlvl(1984) lglchlid(001) nodetype(calc) tmsgrpnbr(calc) autodltdev(no) cmnrcylmt(10 1)

	=== Notes ===		=== Notes ===

ZuluSCSI

PoC — Tue, 25 Aug 2026 11:40:00 GMT

Disk drive support: Caveat added

← Older revision		Revision as of 13:40, 25 August 2026
(3 intermediate revisions by the same user not shown)
Line 119:		Line 119:

	Tested with Firmware 2026-08-07, 9401-150, V4R4: IPL only so far.		Tested with Firmware 2026-08-07, 9401-150, V4R4: IPL only so far.

			=== Disk drive support ===
			The officially released code base is able to present a singular #6717, 8.5 GiB disk drive to the system, initialize, and install SLIC + base OS/400 + LPPs + PTFs.

			* Generate disk image:
			dd if=/dev/zero of=HD6.img bs=522 count=17177940 status=progress
			* ''zuluscsi.ini'':
			[SCSI]
			System = AS400_PPC

			[SCSI6]
			PrefetchBytes = 0

			Caveats:
			* Writes to the emulated disk are very slow compared to reads.
			* One user with a RP2040 reported failure for the disk to be recognized. Prerelease firmware solved the issue.

			Fully tested with Firmware 2026-08-21, 9401-150, V4R4.

	== Current state ==		== Current state ==
	~~In the scope of~~ AS/400's, ~~ZuluSCSI's disk support is still incomplete~~, ~~while~~ CD- ~~and tape emulation are seemingly solid~~. ~~Some progress has been made, but there are still some rough edges~~, ~~normally leading to crash of the Operating System~~ with ~~a given ''System Reference Code''~~.		We have to differ three hardware generations when considering Zulu vs. AS/400:
			{\|class="wikitable"
			!
			!CISC/IMPI, 520 bytes/block disks
			!RISC/SPD, 520/522 bytes/block disks
			!RISC/PCI, 522 bytes/block disks
			\|-
			!CD-ROM
			\|Not supported
			\|Untested
			\|Works
			\|-
			!Tape
			\|Fails, hangs with SRC early.
			\|Untested
			\|Works
			\|-
			!Disk
			\|Fails, hangs with SRC early.
			\|Untested
			\|Works
			\|}

	~~At the moment~~, the ~~firmware supports only~~ a ~~single AS/400 specific DASD device type for PPC-AS (522 Bytes per sector)~~.		All successful tests so far have been based on a ZuluSCSI wide board, while the CISC tests have been done with a ZuluSCSI Blaster.

	==~~= Reports =~~==		== Next ==
	* 2026-08-16, mikerm, ~~9406-170~~, ~~Zulu firmware 2026-08-07. Trying~~ to ~~install V4R4 on~~ the ~~Zulu emulated DASD~~. ~~Disk was created with <code>dd if=/dev/zero of=HD6~~.~~img bs=~~522 ~~count=17177940 status=progress</code><ref>Per directions of one of the firmware developers~~.~~</ref>~~		These features are completed, partially tested, but did not make it to the official releases yet:
	** ~~First try,~~ ''~~prefetch~~'' ~~setting at default (8k): halts at~~ <code>~~B1934505~~</code> ~~after IPL takes place from DASD~~		* More disk profiles, loadable in ''zuluscsi.ini'' via external file ''as400_disk_definitions.txt'', so different types than the built-in 522 bytes, 8.5 GiB #6717 can be assigned.
	** Second try, ''prefetch'' set to 0: <code>~~B6080801~~</code> ~~after IPL takes place from DASD. More progress, and much quicker LIC install, though.~~		** Shellscript to generate more ''as400_disk_definitions.txt'' entries from real disks connected to a SCSI controller when ran under Linux
	** Configuration file used:		** Because of serial numbers currently being hard coded, only one disk per type should be used
	~~[SCSI]~~		* Allowed more memory to accommodate the necessary VPD SCSI pages for multiple disks
	~~LogModeData = 1~~		* Present captured real tape VPD/SCSI data from IBM SLR5/QIC1000 when using <code>Device = "AS400_PPC"</code> or <code>Device = "AS400_CISC"</code> in an ID stanza
	~~System = AS400_BS522~~		* Created a new build profile for the ZuluSCSI Blaster, removing all the add-on code being unneeded when used with AS/400

	== See also ==		== See also ==