Your own AS/400 - Revision history

PoC: /* Noise Level */ typo

2026-03-04T01:31:45Z

Noise Level: typo

← Older revision		Revision as of 03:31, 4 March 2026
Line 33:		Line 33:

	== Noise Level ==		== Noise Level ==
	[[IBM-9401-150-side_flap.jpg\|thumb\|right\|Side flap with bitumen mats applied.]]		[[File:IBM-9401-150-side_flap.jpg\|thumb\|right\|Side flap with bitumen mats applied.]]
	Most older machines are surprisingly silent when initially powered on: Only the (few and huge) fans rotate. Disks will be started one by one by the service processor during the boot sequence.		Most older machines are surprisingly silent when initially powered on: Only the (few and huge) fans rotate. Disks will be started one by one by the service processor during the boot sequence.

PoC: /* Noise Level */ +pic

2026-03-04T01:31:26Z

Noise Level: +pic

← Older revision		Revision as of 03:31, 4 March 2026
Line 33:		Line 33:

	== Noise Level ==		== Noise Level ==
			[[IBM-9401-150-side_flap.jpg\|thumb\|right\|Side flap with bitumen mats applied.]]
	Most older machines are surprisingly silent when initially powered on: Only the (few and huge) fans rotate. Disks will be started one by one by the service processor during the boot sequence.		Most older machines are surprisingly silent when initially powered on: Only the (few and huge) fans rotate. Disks will be started one by one by the service processor during the boot sequence.

PoC: /* Recommendation */ Added pictures

2026-03-04T01:06:14Z

Recommendation: Added pictures

← Older revision		Revision as of 03:06, 4 March 2026
Line 99:		Line 99:

	== Recommendation ==		== Recommendation ==
	~~[[File:IBM-9401-150-main-planar-front.jpg\|thumb\|right\|Mainboard of a model 150]]~~
	~~[[File:IBM-9401-150-main-planar-back.jpg\|thumb\|right\|Mainboard of a model 150, backside]]~~
	If asked for a precise recommendation, I'd say, a 9401-150, equipped with max. memory (192 MB) and three to four 6607 (4 GiB) disks<ref>It is said that you can't IPL from disks larger than 8 GiB. However, you can add larger disks to a given ASP with an 8 GiB IPL source disk.</ref> is nearly optimal:		If asked for a precise recommendation, I'd say, a 9401-150, equipped with max. memory (192 MB) and three to four 6607 (4 GiB) disks<ref>It is said that you can't IPL from disks larger than 8 GiB. However, you can add larger disks to a given ASP with an 8 GiB IPL source disk.</ref> is nearly optimal:
	* Small form factor,		* Small form factor,
Line 120:		Line 118:
	* internal SCSI cable, with corroded contacts between wires and crimped plugs		* internal SCSI cable, with corroded contacts between wires and crimped plugs

	Interestingly, I not yet suffered from a catastrophic disk failure.		Interestingly, I have not yet suffered from a catastrophic disk failure.

			=== 9401 model 150 gallery ===
			<gallery mode="packed">
			File:IBM-9401-150-inside.jpg\|Inside view
			File:IBM-9401-150-main-planar-front.jpg\|Mainboard of a model 150
			File:IBM-9401-150-main-planar-back.jpg\|Mainboard of a model 150, backside
			File:IBM-9401-150-side flap.jpg\|Case side flap with added bitumen sheets
			</gallery>

	== Weblinks ==		== Weblinks ==

PoC: /* Recommendation */ more precise

2024-09-06T22:55:18Z

Recommendation: more precise

← Older revision		Revision as of 00:55, 7 September 2024
Line 118:		Line 118:
	Despite the sheer age of the hardware, the machines usually run flawlessly for years. From my own experience, things which have failed for me over the course of many years:		Despite the sheer age of the hardware, the machines usually run flawlessly for years. From my own experience, things which have failed for me over the course of many years:
	* [[9401-150_Power_Supply_Pinout#PSU_Replacement\|PSU]],<ref>Precisely, the primary side electrolytic capacitors. The PSU can be repaired by someone skilled with a soldering iron by just replacing those caps, which are standard parts.</ref>		* [[9401-150_Power_Supply_Pinout#PSU_Replacement\|PSU]],<ref>Precisely, the primary side electrolytic capacitors. The PSU can be repaired by someone skilled with a soldering iron by just replacing those caps, which are standard parts.</ref>
	* internal SCSI cable.		* internal SCSI cable, with corroded contacts between wires and crimped plugs

	Interestingly, I not yet suffered from a catastrophic disk failure.		Interestingly, I not yet suffered from a catastrophic disk failure.

PoC: /* Y2K issues */ expanded

2024-09-06T22:53:07Z

Y2K issues: expanded

← Older revision		Revision as of 00:53, 7 September 2024
Line 87:		Line 87:

	== Y2K issues ==		== Y2K issues ==
	Very old machines (beige case, CISC CPU, pre 199x) usually run very old OS releases that aren't y2k-safe. One may choose to select a pastime year with a likewise mapping from weekday to actual date to partly work around this issue.		Very old machines (beige case, CISC CPU, pre 199x) usually run very old OS releases that aren't y2k-safe. One may choose to select a pastime year with a likewise mapping from weekday to actual date to partly work around this issue, if the current year is not accepted.

	IBM states<ref>IBM Redbook [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=SG24482900 AS/400 Applications: Year 2000 Enablement & Services Considerations], SG24-4829-00</ref>, Version 3 of OS/400 is „Y2k-enabled“ to different degrees in the minor releases of V3 with appropriate patches (PTFs) applied.		IBM states<ref>IBM Redbook [https://www.ibm.com/resources/publications/OutputPubsDetails?PubID=SG24482900 AS/400 Applications: Year 2000 Enablement & Services Considerations], SG24-4829-00</ref>, Version 3 of OS/400 is „Y2k-enabled“ to different degrees in the minor releases of V3 with appropriate patches (PTFs) applied.

	So far I have not yet discovered adverse effects of y2k issues with a machine running V2R3. Actual calculation errors usually arise from using two digit years when calculations cross the year 2000. This old OS also uses only two digit years, but time has probably progressed far enough into the 2000s, so crossing the 2000 barrier just doesn't happen anymore in day to day use.		So far I have not yet discovered adverse effects of y2k issues with a machine running V2R3. Actual calculation errors usually arise from using two digit years when calculations cross the year 2000. This old OS also uses only two digit years, but time has probably progressed far enough into the 2000s, so crossing the 2000 barrier just doesn't happen anymore in day to day use, and Y2K is no longer relevant.

	== Space requirements ==		== Space requirements ==

PoC: /* Boot time */ typo

2024-02-14T21:59:33Z

Boot time: typo

← Older revision		Revision as of 23:59, 14 February 2024
Line 28:		Line 28:
	Okay, you want to have a big box, because you like it fast. You plan to boot when you decide to tinker around and shut it down when you're done. Drawback is that those machines take awful long to boot. I'm talking about 5..15 Minutes or more, if the system was powered off without proper shutdown. Keep in mind that you probably don't tinker around as much as you intent, because booting the box for just a short test isn't worthwhile the investment in patience. Proper shutdown also takes several minutes.		Okay, you want to have a big box, because you like it fast. You plan to boot when you decide to tinker around and shut it down when you're done. Drawback is that those machines take awful long to boot. I'm talking about 5..15 Minutes or more, if the system was powered off without proper shutdown. Keep in mind that you probably don't tinker around as much as you intent, because booting the box for just a short test isn't worthwhile the investment in patience. Proper shutdown also takes several minutes.

	Think twice. Maybe it's a better idea to have a slower box readily available when you're awake. Since it doesn't draw so much power, it doesn't hurt the pocket equally to have a big box running all the time. Besides that, AS/400s usually can be tasked on a very flexible way to power up and down to certain times on certain days.		Think twice. Maybe it's a better idea to have a slower box readily available when you're awake. Since it doesn't draw so much power, it doesn't hurt the pocket equally to have a big box running all the time. Besides that, AS/400s usually can be tasked in a very flexible way to power up and down to certain times on certain days.

	Boot and shutdown are somewhat I/O intensive tasks. More disks make the box boot and shut down a bit faster.		Boot and shutdown are somewhat I/O intensive tasks. More disks make the box boot and shut down a bit faster.

PoC: /* Power Consumption */ +Link

2024-02-14T21:58:36Z

Power Consumption: +Link

← Older revision		Revision as of 23:58, 14 February 2024
Line 18:		Line 18:
	It is possible that older machines (with SPD-Slots instead of PCI) request a new ''system password'' when the hardware configuration changes. To my knowledge, this password can be calculated by IBM only by providing some output of hardware inventory to IBM. Your mileage may vary.		It is possible that older machines (with SPD-Slots instead of PCI) request a new ''system password'' when the hardware configuration changes. To my knowledge, this password can be calculated by IBM only by providing some output of hardware inventory to IBM. Your mileage may vary.

	Especially power hungry by comparison are integrated PC servers. These are cards that have an INTeL-CPU and dedicated RAM. These allow you to run Netware or Windows directly from virtual disk files on the AS/400 disks. Especially if not in use, these cards draw a good deal of power, because the CPU doesn't get HALT instructions for power saving.<ref>Just like an ordinary PC when displaying BIOS settings screen.</ref> E. g. 2850-011-Adapter: Pentium II@333MHz with 128 MB RAM sucks about 20 W extra power from the power supply.		Especially power hungry by comparison are [[The Integrated PC Servers\|integrated PC servers]]. These are cards that have an INTeL-CPU and dedicated RAM. These allow you to run Netware or Windows directly from virtual disk files on the AS/400 disks. Especially if not in use, these cards draw a good deal of power, because the CPU doesn't get HALT instructions for power saving.<ref>Just like an ordinary PC when displaying BIOS settings screen.</ref> E. g. 2850-011-Adapter: Pentium II@333MHz with 128 MB RAM sucks about 20 W extra power from the power supply.

	The very old 9401-P03 "CISC" Portable [[9401-P03]] draws around 30 W. The low end model 9401-150 is more on the 80 W-end whereas a full blown 9406-S20 with two full disk cages sucks around 320 W from mains. A 9406-800 with just two disks needs around 170 W.<br />		The very old 9401-P03 "CISC" Portable [[9401-P03]] draws around 30 W. The low end model 9401-150 is more on the 80 W-end whereas a full blown 9406-S20 with two full disk cages sucks around 320 W from mains. A 9406-800 with just two disks needs around 170 W.<br />

PoC: /* Power Consumption */ P03

2024-02-14T21:57:27Z

Power Consumption: P03

← Older revision		Revision as of 23:57, 14 February 2024
Line 13:		Line 13:

	== Power Consumption ==		== Power Consumption ==
	Older machines from pre 2000 need most power for spinning their hard disks. You can add 10..12 W of power for every 3,5"-Disk. Depending on model and how much stuff is in there, you can calculate between 80..400 W for a machine.		Older machines from pre 2000 need most power for spinning their hard disks. You can add 10..12 W of power for every 3,5"-Disk. Depending on model and how much stuff is in there, you can calculate between 30..400 W for a machine.

	Every expansion card needs power to operate, even if it is not used. The more cards, the more power. It's usually safe to wade out cards one doesn't need. Some boxes had multiple modems attached to dedicated serial ports. Get rid of them.<br />		Every expansion card needs power to operate, even if it is not used. The more cards, the more power. It's usually safe to wade out cards one doesn't need. Some boxes had multiple modems attached to dedicated serial ports. Get rid of them.<br />
Line 20:		Line 20:
	Especially power hungry by comparison are integrated PC servers. These are cards that have an INTeL-CPU and dedicated RAM. These allow you to run Netware or Windows directly from virtual disk files on the AS/400 disks. Especially if not in use, these cards draw a good deal of power, because the CPU doesn't get HALT instructions for power saving.<ref>Just like an ordinary PC when displaying BIOS settings screen.</ref> E. g. 2850-011-Adapter: Pentium II@333MHz with 128 MB RAM sucks about 20 W extra power from the power supply.		Especially power hungry by comparison are integrated PC servers. These are cards that have an INTeL-CPU and dedicated RAM. These allow you to run Netware or Windows directly from virtual disk files on the AS/400 disks. Especially if not in use, these cards draw a good deal of power, because the CPU doesn't get HALT instructions for power saving.<ref>Just like an ordinary PC when displaying BIOS settings screen.</ref> E. g. 2850-011-Adapter: Pentium II@333MHz with 128 MB RAM sucks about 20 W extra power from the power supply.

	The low end model 9401-150 is more on the 80 W-end whereas a full blown 9406-S20 with two full disk cages sucks around 320 W from mains. A 9406-800 with just two disks needs around 170 W.<br />		The very old 9401-P03 "CISC" Portable [[9401-P03]] draws around 30 W. The low end model 9401-150 is more on the 80 W-end whereas a full blown 9406-S20 with two full disk cages sucks around 320 W from mains. A 9406-800 with just two disks needs around 170 W.<br />
	Standby Usage of a 9401-150 is about 4 W. Standby Usage from a 9406-800 is about 20 W.		Standby Usage of a 9401-150 is about 4 W. Standby Usage from a 9406-800 is about 20 W.

PoC: /* Complexity */ DST

2024-02-14T21:55:30Z

Complexity: DST

← Older revision		Revision as of 23:55, 14 February 2024
Line 8:		Line 8:

	== Complexity ==		== Complexity ==
	Newer hardware with LPAR support is inherently complex to set up and configure. You probably need a Hardware Management Console for proper configuration of LPARs and IPL parameters, and for easy access to a Console. Ethernet ports are virtual and can be used by IBM i lines and probably by DST as a LAN console attachment. Which port corresponds to which entity in IBM i? I got multiple headaches when fighting with a 8203-E4A to get a grip onto how stuff works.		Newer hardware with LPAR support is inherently complex to set up and configure. You probably need a Hardware Management Console for proper configuration of LPARs and IPL parameters, and for easy access to a Console. Ethernet ports are virtual and can be used by IBM i lines and probably by DST<ref>Dedicateed Service Tools, a bit like a PC BIOS setup, but with much broader scope.</ref> as a LAN console attachment. Which port corresponds to which entity in IBM i? I got multiple headaches when fighting with a 8203-E4A to get a grip onto how stuff works.

	Older hardware is much simpler to set up. Twinax Console, Power, Probably LAN attachment, that's it. No virtualization means that physical ports have exactly one logical resource in OS/400.		Older hardware is much simpler to set up. Twinax Console, Power, Probably LAN attachment, that's it. No virtualization means that physical ports have exactly one logical resource in OS/400.

PoC: /* Recommendation */ reworked

2023-08-15T11:22:14Z

Recommendation: reworked

← Older revision		Revision as of 13:22, 15 August 2023
Line 109:		Line 109:
	Drawbacks include:		Drawbacks include:
	* Too slow for frequent usage of SQL in interactive applications,<ref>The [https://en.wikipedia.org/wiki/IBM_RS64#Cobra_and_Muskie IBM RS64 "Cobra" CPU] is clocked at assumedly 49.65 MHz.</ref>		* Too slow for frequent usage of SQL in interactive applications,<ref>The [https://en.wikipedia.org/wiki/IBM_RS64#Cobra_and_Muskie IBM RS64 "Cobra" CPU] is clocked at assumedly 49.65 MHz.</ref>
			* Too slow to meaningfully run the latest supported release (V5R2),<ref>This shows mainly through increased response times. V5R2 occupies much more space on disk compared to V4R5, and that increased amount of data has to be written, read, and processed.</ref>
	* Attach to modern LANs through an ethernet card that runs at 10 Mbit/s only (2723 adapter) or 16 Mbit/s Token Ring (2724 adapter). Usually not a problem since the CPU is easily saturated by a single FTP transfer over TCP/IP via a 2723 Ethernet Adapter. IP is a very resource hungry protocol. And we mostly will run terminal sessions that need only a tiny fraction of the seemingly tiny bandwidth. See also: '''[[Getting Data in and out of your AS/400]]''',		* Attach to modern LANs through an ethernet card that runs at 10 Mbit/s only (2723 adapter) or 16 Mbit/s Token Ring (2724 adapter). Usually not a problem since the CPU is easily saturated by a single FTP transfer over TCP/IP via a 2723 Ethernet Adapter. IP is a very resource hungry protocol. And we mostly will run terminal sessions that need only a tiny fraction of the seemingly tiny bandwidth. See also: '''[[Getting Data in and out of your AS/400]]''',
	* Maybe noisy, depending on the disks,		* Maybe noisy, depending on the disks,
	* Old machine, old OS: Was current around the 2000s.		* Old machine, old OS: Was current around the 2000s.

	Old OS in regard to Programming means: Current fancy RPG features such as <code>/free</code> or <code>/all-free</code> are '''not''' ~~(yet)~~ implemented. Some RPG statements ~~themselves~~ are missing ~~— date/time calculation functions come to mind~~. Many SQL features and commands are '''not''' ~~(yet)~~ implemented. ~~And possibly more~~.		Old OS in regard to Programming means: Current fancy RPG features such as <code>/free</code> or <code>/all-free</code> are '''not''' implemented. Some RPG statements, and BIFs (built-in functions, often starting with the '<code>%</code>' character) are missing. Many SQL features and commands are '''not''' implemented. This short list is not exhaustive.

	Despite the sheer age of the hardware, the machines usually run flawlessly for years. From my own experience, things which have failed for me over the course of many years:		Despite the sheer age of the hardware, the machines usually run flawlessly for years. From my own experience, things which have failed for me over the course of many years:
	* [[9401-150_Power_Supply_Pinout#PSU_Replacement\|PSU]],<ref>Precisely, the primary side electrolytic capacitors. The PSU can be repaired by someone skilled with a soldering iron by just replacing those caps.</ref>		* [[9401-150_Power_Supply_Pinout#PSU_Replacement\|PSU]],<ref>Precisely, the primary side electrolytic capacitors. The PSU can be repaired by someone skilled with a soldering iron by just replacing those caps, which are standard parts.</ref>
	* internal SCSI cable.		* internal SCSI cable.

			Interestingly, I not yet suffered from a catastrophic disk failure.

	== Weblinks ==		== Weblinks ==