IBM P/390 - Unanswered questions

Hardware

  1. Do other FRUs than these exist?

    P/390  PCI   32M    08J5874 4.5 MIPS
P/390  PCI  128M    08J5941 4.5 MIPS
P/390  PCI  128M    08J5882 4.5 MIPS
P/390E PCI  256M    11J4299 7   MIPS
P/390E PCI 1024M    11J5841 7   MIPS
P/390  MCA  CPU     17H5372 4.5 MIPS
P/390  MCA   32M    26H2931
P/390  MCA   96M    26H2978

    It's unclear if these FRUs are real.

    P/390  PCI  128M    08J5812
P/390  PCI  128M    08J5940
P/390  PCI  128M    08J5941
P/390  PCI  128M    08J954102USA

  2. What is the reason for two FRUs (08J5941 and 08J5882) for the 128M model? The two cards have equal functionality, use the same microcode but are different PCB revisions.

  3. What is the purpose of the unpopulated LED footprints DS1, DS2, DS3, DS4, J2 and U49 of FRU 08J5882? If LEDs are mounted, they seems to indicate machine states, but the meaning of the individual LEDs is unclear.

OS/2 software

  1. Version 2.5 and upgrade to 2.5.3 is available, also a 3.x upgrade but no 3.0 base. Where can 3.0 be found?

AIX software

  1. Is there a manual for the TN3270 client program XANT or at least information how to issue Program Attention Keys, especially CLEAR?
  2. Where can one obtain a copy of the TN3270 client program HCON?
  3. Console programs like awscnf seem to be ported from OS/2 in a rather rough manner. The output is in CP437 that AIX isn't able to display properly in dtterm, aixterm or xterm. Was this an accepted defect or is there a known solution to convert the codepage?

Licensed Internal Code

  1. Depending on the architecture mode (370 or ESA) the card is supposed to run in, a different microcode blob is being loaded into the card.

    These are the microcode files that can be found on the FTP site p390.ibm.com and in some other places. Are other (older or newer) files known?

    Filename    Version *          Size   md5sum                           Change date
----------------------------------------------------------------------------------

AWS3900.MCD P3901V01.10        165840 190da12ef5d14a163cf5b5169bc796e3 1996-02-26
AWS3900.MCP P3901V01.20        166632 2925d3c0e67532ea2d6bd8510cb72427 1996-11-01
AWS3900.MCD P3901V01.26        169488 32b9e7adf0e3beb126f5b871fc9cbef5 1997-07-08
AWS3900.MCP P3901V01.29        169800 aefb00d6bebb72f082cb14717f057ad0 2001-03-16

AWS39X0.MCD P3902V01.10        288336 c9b3d8055139d08a1cc5fcb13a5143a6 1996-02-26
AWS39X0.MCP P3902V01.20        292656 b7aa03ecae262384ac8474cac5ddb2ba 1996-11-04
AWS39X0.MCP P3902V01.26        295392 443578fc6a76b91dc77c6095b72711be 1997-07-08
AWS39X0.MCD P3902V01.28        304968 db11f2859e767d64cb84f4676e5575cf 1998-04-06
AWS39X0.MCP P3902V01.29        305592 b900000a38580881fa7ca79ff1bc4c6c 1998-08-28
AWS39X0.MCP P3902V01.2A        308880 e68f2dbea00a64fb527d821957dc4866 1999-05-14
AWS39X0.MCP P3902V01.2D        309528 93a305e9e8f42a78c1873aacd5a533df 2000-09-10

AWS3901.MCP P390E S/370 V02.10 155712 db56fc4d6f1060b825ad87ccfe0f783c 1998-10-12
AWS3901.MCP P390E S/370 V02.12 155880 42dc8c7c1c2ab9269df5aebe8f9eb365 1999-10-22

AWS39X1.MCP P390E S/390 V02.10 299400 4f490e5a0bbd4a885e92c08f6f526f58 1998-10-12
AWS39X1.MCP P390E S/390 V02.11 347256 158c5b9500a6566920bc59a72ccdf65b 1999-05-14
AWS39X1.MCP P390E S/390 V02.16 360768 9965c88c7c67e34bd2a685a9ab69b7c7 2001-04-06

* dd if=<filename> skip=1 count=23 bs=1 status=none; echo