The Application System/400 (AS/400) is an International Business Machines minicomputer for general business and departmental use, introduced in 1988 and still in production under the names iSeries and i5. The AS/400 is an object based system with an integrated database that was designed to implement Edgar F. Codd relational database model in the operating system and hardware. All software necessary to run this computer is included and integrated. More than 2,500 business software applications were available when the first AS/400 was delivered in 1988. The AS/400 was the follow-on to the System/38 database machine, announced by IBM in 1978 and delivered in 1980. The first AS/400 systems (known by the development code names Silverlake and Olympic) were delivered in 1988, and the product line has been refreshed continually since then. IBM renamed the AS/400 to iSeries in 2000, as part of its e-Server branding intiative. The product line was further extended in 2004 with the introduction of the i5 servers, the first to utilize the IBM IBM_POWER#Implementations processor. The AS/400 was the first general purpose computer system to attain a C2 security rating from the National Security Agency, and in 1995 was first to employ a 64-bit processor and operating system. The architecture of the system allows for future implementation of 128-bit processors when they become available. Existing programs will utilize the new hardware without modification. Features include an extremely fast DBMS, a menu-driven interface, multi-user support, terminals (IBM 5250) and printers, security, communications and an extensive library-based operating system, OS/400. The big selling point is that applications can run without modification on any model in the product line, from small, single processor machines up to those with 64 multi-core CPUs. The machine was originally based on a custom IBM Complex Instruction Set Computer Central processing unit which used a CPU architecture known as Internal MicroProgrammed Interface (IMPI). It was later migrated to a PowerPC based RISC CPU family eventually known as RS64. The latest models are based on the POWER5 (announced 4 May 2004) processor. The machine survives because its Instruction set architecture (called TIMI for "Technology Independent Machine Interface" by IBM) allows the operating system and application programs to take advantage of advances in hardware and software without recompilation. This means that a program written and compiled on a S/38 can be run as a native 64 bit program. The HAL allows a system that costs $9000 to run the exact same operating system and software as a $2 million system. The system can concurrently run multiple operating systems (i5/OS (OS/400), Linux, AIX) natively, and runs Windows Server and Linux on one or more single cpu blade servers or externally attached mutiple cpu servers when installed. The 64-bit design provides for the seamless addressing of up to 16 exabytes (16 million terabytes) of storage. The AS/400 enforces the use of the TIMI virtual instruction set for all user mode programs; it is not possible for such programs to utilise the instruction set of the underlying CPU, thus ensuring hardware independence. This is conceptually somewhat similar to the virtual-machine architecture of programming environments such as SmallTalk, Java programming language and .NET. The key difference is that it is embedded so deeply into the AS/400's design as to make all applications and even the bulk of its operating systems binary-compatible across different processor families. The AS/400's instruction set defines all pointers as 128-bit to allow seamless transition from older to new processor generations. Another feature that was recently introduced to the AS/400, LPAR, came from IBM's mainframe line of computers. LPAR (Logical PARtitioning) facilitates running multiple instances of operating systems simultaneously on one AS/400 unit. A system setup with LPAR can even run different operating systems on different partitions while ensuring that one OS cannot run over the memory or resources of another. Each LPAR is given a portion of system resources (memory, hard disk space, and CPU time) via a system of weights that determines where unused resources are allocated at any given time. The OSes supported (and commonly used) under the LPAR scheme are OS/400, AIX operating system and Linux. Even though AIX can now be natively run in a LPAR partition, the original implemenation was to allow AIX programs to be ported to the PASE environment. AIX programs ARE binary compatible with OS/400 when using OS/400's PASE (Portable Applications System Environment). PASE is essentially "an operating system within an operating system", supporting the most recent stable version of AIX. Binaries need to be re-compiled on the AIX system, with 16-bit (quadword) pointer alignment enabled. Once the program is compiled with this option, the executable can be FTP-ed to the AS/400, and executed under the PASE Korn Shell. Additionally, tasks such as handling record locks and queuing updates are managed automatically by the system, making high-speed, multiuser applications easy to create, maintain, and extremely reliable. Programming languages available for this machine include RPG (programming language), assembly language, C programming language, C Plus Plus, Java_platform, COBOL, SQL, BASIC programming language, PHP, PL/I, and REXX. Several CASE tools are available: Synon, AS/SET, and Lansa. Commands in the AS/400 Command Language are promptable and most provide cursor sensitive help to make entering parameters easier. A command consists of a three letter verb and a subject part. This is intended to make it easy to understand CL code. Examples: * CRTUSRPRF - Create user profile * DLTLIB - Delete library * CPYF - Copy file * WRKACTJOB - Work Active Jobs It was designed as the successor of the IBM System/38 and the IBM System/36. The programmers that worked on OS/400, the operating system of the AS/400, did not have a UNIX background. Dr. Frank Soltis, the head architect, says that this is the main difference between this and any other operating system. Despite the lack of "UNIXy" background, the AS/400 has over the years, picked up the programming/runtime model found on UNIX, Linux, and PC systems. Traditional AS/400 programming is a "one-stop shop", where a programmer writes computer code, Compiler the code, and then executes the code. There is no link step that is found in other environments. However, in 1995, that changed. IBM re-christened the one-stop shop programming style "OPM" (for Original Programming Model) and introduced a new language paradigm called "ILE" (for Integrated Language Environment). ILE had significant enhancements over OPM, including the ability to create modules (similar to .obj or .lib files), and then bind (link) the modules together into a single executable. The executable could be created as a program or a service program (service programs are similar to .lib or .dll files). The real power of the ILE environment is in the "integrated" aspect, however. Modules in ILE-compliant languages (RPG, COBOL, C, C++, and CL) could be created and bound together. For the first time, AS/400 programmers could exploit the strengths of each ILE-compliant language and create programs. Also, with the introduction of service programs, standard routines could be externalized more easily, and increase modularity. To ensure proper migration to the ILE environment, OPM RPG and COBOL programs could be migrated to ILE easily. Interoperation with the Java programming language language is also supported, though not as tightly as to the ILE languages. The iSeries Java implementation is distinguished by the depth of its embedment in the operating system. == See also == *AS/400 Command Language *AS/400 Libraries *AS/400 object *OS/400 *IBM 5250 *iSeries Architecture == External links == *[http://www-1.ibm.com/servers/eserver/iseries/ ''iSeries Home Page''] at IBM *[http://www.midrange.com/ ''midrange.com -- i5 / iSeries / AS400 technical discussion mailing lists and more''] AS/400 IBM hardware
== Precursor to Smalltalk == The article suggests that the AS400's virtual intruction set might be a precursor to a programming language whose standard version, Smalltalk-80, was released EIGHT YEARS before the AS400 line was released. Smalltalk itself had been around for some considerable time bbefore that. This is something of a reach, to say the least. Anyone care to justify this claim, before I remove it? User:Lproven 15:54, 20 Apr 2005 (UTC) :Agreed, remove it. The entire comparison of the S/38 / AS/400 / iSeries MI to platforms like Java and .NET (which are in themselves fairly different) is pretty weak; I'll try to think of some better phrasing for that section. -- User:Uberpenguin 16:16, 2005 Apr 20 (UTC) ::It is done. I've reworded the entire paragraph to remove the claim of primacy but retain the association of ideas. User:Lproven 13:09, 23 Apr 2005 (UTC) ---- "Said to be" means that it is up for discussion. It is not. I have seen OLD programs run over time. This is not a sales pitch. If you are a competent programmer and have source you WILL recompile programs to make use of the latest compiler improvements. Removing Mr Soltis as the source of the statement of the programmers working on OS/400 and licensed programs is silly as without it makes no sense anymore. What is the point of explaining about verbs etc without mentioning its benefit? The point that all software is included and integrated, is what differentiates it from all other systems. So it is relevant. The kernel and the hardware related code are essentially different; this allows IBM competitors to create an OS on the bare machine. This is a result of lawsuits relating to mainframe OS clones. == iSeries redirect == I changed iSeries to redirect here once more. Upon reading through the article carefully (and posting comments on that article's Talk:ISeries), I found no information that wasn't covered better and more thoroughly in the AS/400 article. The iSeries article was basically just a list of features and a short section on criticisms of the system, which is a good idea but was poorly executed on that page. "iSeries" is nothing more than a rebranding of the AS/400 line. It doesn't suggest any major architectural changes (that is, any changes more significant than the AS/400 has seen in the past; the TIMI is what really makes the AS/400 / iSeries unique), so I can't see any reason why iSeries shouldn't redirect here. Please post your comments if you feel differently. -- User:Uberpenguin 21:11, 2005 Apr 18 (UTC ===Just my opinion=== As I am new to using wikipedia, but not the AS/400 or iSeries, I may have not laid out my ideas in the best way. I have tried to be factual and ub-biased, except the misunderstood section and have tried to correct any errors in what I originally thought, but it bothered me that there wasn't an iSeries entry. I am aware that iSeries is just a rename of AS/400 and most people who have used it still refer to it as AS/400. If you look at the entries for Windows, there are entries for win95, xp, 2000, etc. the argument could be there is no need for more than a single Microsoft entry or Linux entry. I mean the different entries for those operating systems are only different versions as well. In fact it hasn't been OS/400 since V4R5, 5 years ago, i5/OS is now at V5R3. :I don't believe this argument holds up very well. Win9x and WinNT are two VERY distinct OSes; one based on an aged MS-DOS code base, and the other based on Dave Cutler's work in designing the NT kernel and API. Windows 2000 and XP are arguably very similar (their kernel revision numbers are 5.0 and 5.1, respectively), but have different articles because their target is very different (desktop rather than server) and a lot of things were changed to reflect that new target. If you wanted to apply this example to why there should be an iSeries article, you might as well create an article for every revision of OS/400... -- User:Uberpenguin 05:45, 2005 Apr 22 (UTC) Actaully I started creating the iSeries article, based off the layout of the Windows 2000 article. My feeling was that if someone had a interest or heard about this system somehow, it wouldn't say much if all it did was redirect it to the AS/400 article. Their impression would be "Oh that old system". From a PR stand point the rename, didn't change the system, but there has been substantial additions to its capabilities in the last 5 years. It is why I tried to add a lot of links, so someone could find out more, if they wanted to, not just the TIMI, which is important, but not the only thing which makes iSeries different than other operating systems. :I appreciate your good intentions, but as I stated before, the format left something to be desired and wasn't a very good representation of Wikipedia style and convention. In its last state, the iSeries article really resembled a product datasheet or bullet-point list of features, not a well-fleshed out discussion of the relevance of those features, how they compare with other OSes, etc. Also, this isn't the appropriate place to be endorsing a 'PR stand point.' People who have a bias about 'that old system' aren't necessarily going to be instantly swayed by a fancy new title (I do realize the irony in this, as it's exactly what IBM has done). However, there is a commonly thrown-around and often agonized over editing concept here called NPOV, which basically means that articles should try to be accurate and factual, not supporting one opinion or another. In other words, the iSeries article didn't cover much material that this article does not, but this one follows writing and style conventions better. -- User:Uberpenguin 05:45, 2005 Apr 22 (UTC) My personal opinion after the last 10 years of working with AS/400/iSeries, as well as the alternatives, is there is no better OS or computer system. The point of the misunderstood system section, if not well done, was to highlight what is positive about this system, which has often been ignored, even by IBM, but usually by people who have never used it, or assume it is only a text only system and GUI's just automatically make alternatives better. My feeling is the iSeries article did have value. I don't consider myself some iSeries expert, just enthusiastic and I would have appreciated any help to make it better, including adding different pictures, but I think over the last couple of weeks I saw one change made by someone else. Whether the article was changed from what I did, I really don't care, but not having an iSeries entry does a disservice to this system and to people who may be interested in finding out more about it. nstelmack :As another long-time user of IBM machines (System/34 on), I do understand what the purpose of the 'Misunderstood system' section was, and do think it's a good idea. However, whenever something like that is included in an article, it is good practice to also include a section of criticisms to counterpoint the praise and try to keep a non-biased tone in the article. I'm not at all against bringing the section back, but I think more should be added to it in the way of valid criticism (most of the criticisms you brought up were trivial, though very common). :Right now, I still don't really see much justification in having an iSeries article simply because there have not been any enormous changes to the system since its rebranding. Of course there have been noteworthy updates to the hardware architecture (which is covered in the IBM POWER article since the AS/400 has been on a more or less microcomputer architecture for a while) and OS/400 itself, but they aren't major enough (in my mind) to merit another article when they could live just as happily here. Thanks for your remarks, and I hope you'll stick around Wikipedia and continue making edits! I'll try to get some other folks to weigh in as well. -- User:Uberpenguin 05:45, 2005 Apr 22 (UTC) == first 64 bit? == The Alpha was introduced in 1992. How is AS/400 "in 1995 was first to employ a 64-bit processor and operating system."? :And the MIPS R4000 was introduced in 1991 (I think; it could have been 1990)... Hmm... I've never noticed this in the article before; it indeed seems spurious. Let me do some research and I'll change it. -- User:Uberpenguin 02:02, 2005 May 28 (UTC)
IBM hardware Minicomputers
See other meanings of words starting from letter:
Words begining with AS/400:
AS/400
AS/400
AS/400
AS/400_Command_Language
AS/400_Command_Language
AS/400_Libraries
AS/400_library
AS/400_Library_List
AS/400_object
AS/400_Objects
AS/400
The Application System/400 (AS/400) is an International Business Machines minicomputer for general business and departmental use, introduced in 1988 and still in production under the names iSeries and i5. The AS/400 is an object based system with an integrated database that was designed to implement Edgar F. Codd relational database model in the operating system and hardware. All software necessary to run this computer is included and integrated. More than 2,500 business software applications were available when the first AS/400 was delivered in 1988. The AS/400 was the follow-on to the System/38 database machine, announced by IBM in 1978 and delivered in 1980. The first AS/400 systems (known by the development code names Silverlake and Olympic) were delivered in 1988, and the product line has been refreshed continually since then. IBM renamed the AS/400 to iSeries in 2000, as part of its e-Server branding intiative. The product line was further extended in 2004 with the introduction of the i5 servers, the first to utilize the IBM IBM_POWER#Implementations processor. The AS/400 was the first general purpose computer system to attain a C2 security rating from the National Security Agency, and in 1995 was first to employ a 64-bit processor and operating system. The architecture of the system allows for future implementation of 128-bit processors when they become available. Existing programs will utilize the new hardware without modification. Features include an extremely fast DBMS, a menu-driven interface, multi-user support, terminals (IBM 5250) and printers, security, communications and an extensive library-based operating system, OS/400. The big selling point is that applications can run without modification on any model in the product line, from small, single processor machines up to those with 64 multi-core CPUs. The machine was originally based on a custom IBM Complex Instruction Set Computer Central processing unit which used a CPU architecture known as Internal MicroProgrammed Interface (IMPI). It was later migrated to a PowerPC based RISC CPU family eventually known as RS64. The latest models are based on the POWER5 (announced 4 May 2004) processor. The machine survives because its Instruction set architecture (called TIMI for "Technology Independent Machine Interface" by IBM) allows the operating system and application programs to take advantage of advances in hardware and software without recompilation. This means that a program written and compiled on a S/38 can be run as a native 64 bit program. The HAL allows a system that costs $9000 to run the exact same operating system and software as a $2 million system. The system can concurrently run multiple operating systems (i5/OS (OS/400), Linux, AIX) natively, and runs Windows Server and Linux on one or more single cpu blade servers or externally attached mutiple cpu servers when installed. The 64-bit design provides for the seamless addressing of up to 16 exabytes (16 million terabytes) of storage. The AS/400 enforces the use of the TIMI virtual instruction set for all user mode programs; it is not possible for such programs to utilise the instruction set of the underlying CPU, thus ensuring hardware independence. This is conceptually somewhat similar to the virtual-machine architecture of programming environments such as SmallTalk, Java programming language and .NET. The key difference is that it is embedded so deeply into the AS/400's design as to make all applications and even the bulk of its operating systems binary-compatible across different processor families. The AS/400's instruction set defines all pointers as 128-bit to allow seamless transition from older to new processor generations. Another feature that was recently introduced to the AS/400, LPAR, came from IBM's mainframe line of computers. LPAR (Logical PARtitioning) facilitates running multiple instances of operating systems simultaneously on one AS/400 unit. A system setup with LPAR can even run different operating systems on different partitions while ensuring that one OS cannot run over the memory or resources of another. Each LPAR is given a portion of system resources (memory, hard disk space, and CPU time) via a system of weights that determines where unused resources are allocated at any given time. The OSes supported (and commonly used) under the LPAR scheme are OS/400, AIX operating system and Linux. Even though AIX can now be natively run in a LPAR partition, the original implemenation was to allow AIX programs to be ported to the PASE environment. AIX programs ARE binary compatible with OS/400 when using OS/400's PASE (Portable Applications System Environment). PASE is essentially "an operating system within an operating system", supporting the most recent stable version of AIX. Binaries need to be re-compiled on the AIX system, with 16-bit (quadword) pointer alignment enabled. Once the program is compiled with this option, the executable can be FTP-ed to the AS/400, and executed under the PASE Korn Shell. Additionally, tasks such as handling record locks and queuing updates are managed automatically by the system, making high-speed, multiuser applications easy to create, maintain, and extremely reliable. Programming languages available for this machine include RPG (programming language), assembly language, C programming language, C Plus Plus, Java_platform, COBOL, SQL, BASIC programming language, PHP, PL/I, and REXX. Several CASE tools are available: Synon, AS/SET, and Lansa. Commands in the AS/400 Command Language are promptable and most provide cursor sensitive help to make entering parameters easier. A command consists of a three letter verb and a subject part. This is intended to make it easy to understand CL code. Examples: * CRTUSRPRF - Create user profile * DLTLIB - Delete library * CPYF - Copy file * WRKACTJOB - Work Active Jobs It was designed as the successor of the IBM System/38 and the IBM System/36. The programmers that worked on OS/400, the operating system of the AS/400, did not have a UNIX background. Dr. Frank Soltis, the head architect, says that this is the main difference between this and any other operating system. Despite the lack of "UNIXy" background, the AS/400 has over the years, picked up the programming/runtime model found on UNIX, Linux, and PC systems. Traditional AS/400 programming is a "one-stop shop", where a programmer writes computer code, Compiler the code, and then executes the code. There is no link step that is found in other environments. However, in 1995, that changed. IBM re-christened the one-stop shop programming style "OPM" (for Original Programming Model) and introduced a new language paradigm called "ILE" (for Integrated Language Environment). ILE had significant enhancements over OPM, including the ability to create modules (similar to .obj or .lib files), and then bind (link) the modules together into a single executable. The executable could be created as a program or a service program (service programs are similar to .lib or .dll files). The real power of the ILE environment is in the "integrated" aspect, however. Modules in ILE-compliant languages (RPG, COBOL, C, C++, and CL) could be created and bound together. For the first time, AS/400 programmers could exploit the strengths of each ILE-compliant language and create programs. Also, with the introduction of service programs, standard routines could be externalized more easily, and increase modularity. To ensure proper migration to the ILE environment, OPM RPG and COBOL programs could be migrated to ILE easily. Interoperation with the Java programming language language is also supported, though not as tightly as to the ILE languages. The iSeries Java implementation is distinguished by the depth of its embedment in the operating system. == See also == *AS/400 Command Language *AS/400 Libraries *AS/400 object *OS/400 *IBM 5250 *iSeries Architecture == External links == *[http://www-1.ibm.com/servers/eserver/iseries/ ''iSeries Home Page''] at IBM *[http://www.midrange.com/ ''midrange.com -- i5 / iSeries / AS400 technical discussion mailing lists and more''] AS/400 IBM hardware
AS/400
== Precursor to Smalltalk == The article suggests that the AS400's virtual intruction set might be a precursor to a programming language whose standard version, Smalltalk-80, was released EIGHT YEARS before the AS400 line was released. Smalltalk itself had been around for some considerable time bbefore that. This is something of a reach, to say the least. Anyone care to justify this claim, before I remove it? User:Lproven 15:54, 20 Apr 2005 (UTC) :Agreed, remove it. The entire comparison of the S/38 / AS/400 / iSeries MI to platforms like Java and .NET (which are in themselves fairly different) is pretty weak; I'll try to think of some better phrasing for that section. -- User:Uberpenguin 16:16, 2005 Apr 20 (UTC) ::It is done. I've reworded the entire paragraph to remove the claim of primacy but retain the association of ideas. User:Lproven 13:09, 23 Apr 2005 (UTC) ---- "Said to be" means that it is up for discussion. It is not. I have seen OLD programs run over time. This is not a sales pitch. If you are a competent programmer and have source you WILL recompile programs to make use of the latest compiler improvements. Removing Mr Soltis as the source of the statement of the programmers working on OS/400 and licensed programs is silly as without it makes no sense anymore. What is the point of explaining about verbs etc without mentioning its benefit? The point that all software is included and integrated, is what differentiates it from all other systems. So it is relevant. The kernel and the hardware related code are essentially different; this allows IBM competitors to create an OS on the bare machine. This is a result of lawsuits relating to mainframe OS clones. == iSeries redirect == I changed iSeries to redirect here once more. Upon reading through the article carefully (and posting comments on that article's Talk:ISeries), I found no information that wasn't covered better and more thoroughly in the AS/400 article. The iSeries article was basically just a list of features and a short section on criticisms of the system, which is a good idea but was poorly executed on that page. "iSeries" is nothing more than a rebranding of the AS/400 line. It doesn't suggest any major architectural changes (that is, any changes more significant than the AS/400 has seen in the past; the TIMI is what really makes the AS/400 / iSeries unique), so I can't see any reason why iSeries shouldn't redirect here. Please post your comments if you feel differently. -- User:Uberpenguin 21:11, 2005 Apr 18 (UTC ===Just my opinion=== As I am new to using wikipedia, but not the AS/400 or iSeries, I may have not laid out my ideas in the best way. I have tried to be factual and ub-biased, except the misunderstood section and have tried to correct any errors in what I originally thought, but it bothered me that there wasn't an iSeries entry. I am aware that iSeries is just a rename of AS/400 and most people who have used it still refer to it as AS/400. If you look at the entries for Windows, there are entries for win95, xp, 2000, etc. the argument could be there is no need for more than a single Microsoft entry or Linux entry. I mean the different entries for those operating systems are only different versions as well. In fact it hasn't been OS/400 since V4R5, 5 years ago, i5/OS is now at V5R3. :I don't believe this argument holds up very well. Win9x and WinNT are two VERY distinct OSes; one based on an aged MS-DOS code base, and the other based on Dave Cutler's work in designing the NT kernel and API. Windows 2000 and XP are arguably very similar (their kernel revision numbers are 5.0 and 5.1, respectively), but have different articles because their target is very different (desktop rather than server) and a lot of things were changed to reflect that new target. If you wanted to apply this example to why there should be an iSeries article, you might as well create an article for every revision of OS/400... -- User:Uberpenguin 05:45, 2005 Apr 22 (UTC) Actaully I started creating the iSeries article, based off the layout of the Windows 2000 article. My feeling was that if someone had a interest or heard about this system somehow, it wouldn't say much if all it did was redirect it to the AS/400 article. Their impression would be "Oh that old system". From a PR stand point the rename, didn't change the system, but there has been substantial additions to its capabilities in the last 5 years. It is why I tried to add a lot of links, so someone could find out more, if they wanted to, not just the TIMI, which is important, but not the only thing which makes iSeries different than other operating systems. :I appreciate your good intentions, but as I stated before, the format left something to be desired and wasn't a very good representation of Wikipedia style and convention. In its last state, the iSeries article really resembled a product datasheet or bullet-point list of features, not a well-fleshed out discussion of the relevance of those features, how they compare with other OSes, etc. Also, this isn't the appropriate place to be endorsing a 'PR stand point.' People who have a bias about 'that old system' aren't necessarily going to be instantly swayed by a fancy new title (I do realize the irony in this, as it's exactly what IBM has done). However, there is a commonly thrown-around and often agonized over editing concept here called NPOV, which basically means that articles should try to be accurate and factual, not supporting one opinion or another. In other words, the iSeries article didn't cover much material that this article does not, but this one follows writing and style conventions better. -- User:Uberpenguin 05:45, 2005 Apr 22 (UTC) My personal opinion after the last 10 years of working with AS/400/iSeries, as well as the alternatives, is there is no better OS or computer system. The point of the misunderstood system section, if not well done, was to highlight what is positive about this system, which has often been ignored, even by IBM, but usually by people who have never used it, or assume it is only a text only system and GUI's just automatically make alternatives better. My feeling is the iSeries article did have value. I don't consider myself some iSeries expert, just enthusiastic and I would have appreciated any help to make it better, including adding different pictures, but I think over the last couple of weeks I saw one change made by someone else. Whether the article was changed from what I did, I really don't care, but not having an iSeries entry does a disservice to this system and to people who may be interested in finding out more about it. nstelmack :As another long-time user of IBM machines (System/34 on), I do understand what the purpose of the 'Misunderstood system' section was, and do think it's a good idea. However, whenever something like that is included in an article, it is good practice to also include a section of criticisms to counterpoint the praise and try to keep a non-biased tone in the article. I'm not at all against bringing the section back, but I think more should be added to it in the way of valid criticism (most of the criticisms you brought up were trivial, though very common). :Right now, I still don't really see much justification in having an iSeries article simply because there have not been any enormous changes to the system since its rebranding. Of course there have been noteworthy updates to the hardware architecture (which is covered in the IBM POWER article since the AS/400 has been on a more or less microcomputer architecture for a while) and OS/400 itself, but they aren't major enough (in my mind) to merit another article when they could live just as happily here. Thanks for your remarks, and I hope you'll stick around Wikipedia and continue making edits! I'll try to get some other folks to weigh in as well. -- User:Uberpenguin 05:45, 2005 Apr 22 (UTC) == first 64 bit? == The Alpha was introduced in 1992. How is AS/400 "in 1995 was first to employ a 64-bit processor and operating system."? :And the MIPS R4000 was introduced in 1991 (I think; it could have been 1990)... Hmm... I've never noticed this in the article before; it indeed seems spurious. Let me do some research and I'll change it. -- User:Uberpenguin 02:02, 2005 May 28 (UTC)
AS/400
IBM hardware Minicomputers
See other meanings of words starting from letter:
A
AB | AC | AD | AE | AF | AG | AH | AI | AJ | AK | AL | AM | AN | AO | AP | AR | AS | AT | AU | AW | AX | AY | AZ |Words begining with AS/400:
AS/400
AS/400
AS/400
AS/400_Command_Language
AS/400_Command_Language
AS/400_Libraries
AS/400_library
AS/400_Library_List
AS/400_object
AS/400_Objects
Sponsored links: praca.
These materials are based on Wikipedia and licensed under the GNU FDL
YouTube.com videos better site than Turbo Tax 2007
