Re: IOCP for MP2003-204
FWIW, we definitely ran ESA 2.30 on our MP2003. It was so long ago I can't recall if we needed a PTF for processor support or not, though. Roland P. Chung wrote: Hello all Listers, thanks to all. I think I should let you guys know the outcome of this project. With an IBM ROC helping me all afternoon yesterday, we finally conclued that it may be because of VM/ESA 2.30 is lecking maintenances to be able to handle the newer hardware (MP2003 and IBM 2105-F20 Shark). The VM was been instlled sometimes in October, 1998 and have no services applied to it since. Talking about stable - VM is the best.
Re: IOCP for MP2003-204
Hello all Listers, thanks to all. I think I should let you guys know the outcome of this project. With an IBM ROC helping me all afternoon yesterday, we finally conclued that it may be because of VM/ESA 2.30 is lecking maintenances to be able to handle the newer hardware (MP2003 and IBM 2105-F20 Shark). The VM was been instlled sometimes in October, 1998 and have no services applied to it since. Talking about stable - VM is the best. No matter how we twisted the IOCDS, we were getting the exact DISABLED WAIT PSW. We felt that when CP sends out the reset to all the channels when IPLed, it went into DISABLED WAIT because it does not understands the return code coming back from the channel/hardware. This is a great experience for me to be involved in the middle of a 'lack of planning', 'cold turkey' CPU upgrade project. They backs up the old O/S DASDs, shuts down the old system, rolls in and installs the new hardware, and starts restore. Hopefully the system would run just like in the new hardware. No parallel...no testing... Ummm. We recommanded to upgrade to VVM 4.40 and try again. This time, I will do all the needed preparation before I drop in again. That is enough. I have been taken up a lot of the bandwidth in this List lately. Thanks again for all the help. You guys are the greatest! Regards, ...Roland --- "Roland P. Chung" <[EMAIL PROTECTED]> wrote: > Hi George, I have 5 CPOWNED volumes. I have used ICKDSF > to formated and DDR restored them all. The other 59 DASDs > are for user DATA. I just put a volume number on. > > The DISABLE WAIT PSW is 000A9025 - and the > explaination is; "SCP initialiated reset of the I/O > interface". Maybe something I should not have included in > the IOCDS? Let me check. > > Regards, > > ...Roland > > George Haddad <[EMAIL PROTECTED]> wrote: > If any - snipped --
Re: IOCP for MP2003-204
SYSC is the HMC Integrated "C"onsole - a linemode beast requiring user of the awkwardly defined syntax: VINPUT VMSG command_text_here SYSG is the HMC Integrated 3270 Console - I remember it as a "G"RAF console, as in: CP DEFINE GRAF 3270 Both work, but differently... SYSG is a regular 3270 emulator console (with a very frustrating and weirdly customizable) keyboard. Of the two, I'd choose SYSG every time. Mike Walter Hewitt Associates The opinions expressed herein are mine alone, not my employer's. "Steve Gentry" <[EMAIL PROTECTED]> Sent by: "The IBM z/VM Operating System" 06/19/2006 01:29 PM Please respond to "The IBM z/VM Operating System" To IBMVM@LISTSERV.UARK.EDU cc Subject Re: IOCP for MP2003-204 Is it SYSG or SYSC? Kris Buelens <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System 06/19/2006 12:21 PM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: IOCP for MP2003-204 SYSG was already supported on 9672, with a recent EC-level. I don't know about MP3000. VM/ESA 2.3 surely did not support SYSG; z/VM 4.2 or 4.4 was the first to support SYSG. Kris, IBM Belgium, VM customer support The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited.
Re: IOCP for MP2003-204
On 6/19/06, Steve Gentry <[EMAIL PROTECTED]> wrote: Is it SYSG or SYSC? Yes ;-) SYSC is the linemode interface in the HMC (the one that is emulated by CP throught the VINPUT stuff) and SYSG is the (more recent) 3270-emulator sessions on the HMC. -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
Re: IOCP for MP2003-204
Is it SYSG or SYSC? Kris Buelens <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System 06/19/2006 12:21 PM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: IOCP for MP2003-204 SYSG was already supported on 9672, with a recent EC-level. I don't know about MP3000. VM/ESA 2.3 surely did not support SYSG; z/VM 4.2 or 4.4 was the first to support SYSG. Kris, IBM Belgium, VM customer support
Re: IOCP for MP2003-204
SYSG was already supported on 9672, with a recent EC-level. I don't know about MP3000. VM/ESA 2.3 surely did not support SYSG; z/VM 4.2 or 4.4 was the first to support SYSG. Kris, IBM Belgium, VM customer support
Re: IOCP for MP2003-204
Hi George, I have 5 CPOWNED volumes. I have used ICKDSF to formated and DDR restored them all. The other 59 DASDs are for user DATA. I just put a volume number on. The DISABLE WAIT PSW is 000A9025 - and the explaination is; "SCP initialiated reset of the I/O interface". Maybe something I should not have included in the IOCDS? Let me check. Regards, ...Roland George Haddad <[EMAIL PROTECTED]> wrote: If any of these DASD are in your CP-owned list, be sure to FORMAT the CP areas as well as defining the Labels. Especially if they are PAGE areas. Bad things have happened to us in the past trying to page to an un-formatted area.As another poster said, please pass on your Disabled Wait PSW as that will most likely pinpoint your current woes.Roland P. Chung wrote:> Thanks George I over the hump right now... I managed to get a IOCDS created on Sunday that gave me access to the tape, 3278's and DASDs.> > Now, I am tying to load the CP. It is not cooperating yet. Nowhere to check why it went into DISABLE WAIT! Maybe because I was to lazy to type in all the command using the standalone ICKDSF. I have not initialized all the other 59 3390-3 and CP is getting upset. I am in the process of using ICKDSF to do a quick initialize putting a volume seriam number on these DASDs and try again. Wish me luck.> > This is a classic case of "lack of planning and totally reflected on me" ^e^ ...> > Thanks again.> > ..Roland>>>
Re: IOCP for MP2003-204
If any of these DASD are in your CP-owned list, be sure to FORMAT the CP areas as well as defining the Labels. Especially if they are PAGE areas. Bad things have happened to us in the past trying to page to an un-formatted area. As another poster said, please pass on your Disabled Wait PSW as that will most likely pinpoint your current woes. Roland P. Chung wrote: Thanks George I over the hump right now... I managed to get a IOCDS created on Sunday that gave me access to the tape, 3278's and DASDs. Now, I am tying to load the CP. It is not cooperating yet. Nowhere to check why it went into DISABLE WAIT! Maybe because I was to lazy to type in all the command using the standalone ICKDSF. I have not initialized all the other 59 3390-3 and CP is getting upset. I am in the process of using ICKDSF to do a quick initialize putting a volume seriam number on these DASDs and try again. Wish me luck. This is a classic case of "lack of planning and totally reflected on me" ^e^ ... Thanks again. ..Roland
Re: IOCP for MP2003-204
Roland Can you post the Disable Wait PSW? eric Eric Schadow Mainframe Technical Support www.davisvision.com The information contained in this communication is intended only for the use of the recipient(s) named above. It may contain information that is privileged or confidential, and may be protected by State and/or Federal Regulations. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, or copying of this communication, or any of its contents, is strictly prohibited. If you have received this communication in error, please return it to the sender immediately and delete the original message and any copy of it from your computer system. If you have any questions concerning this message, please contact the sender.
Re: IOCP for MP2003-204
Thanks George I over the hump right now... I managed to get a IOCDS created on Sunday that gave me access to the tape, 3278's and DASDs. Now, I am tying to load the CP. It is not cooperating yet. Nowhere to check why it went into DISABLE WAIT! Maybe because I was to lazy to type in all the command using the standalone ICKDSF. I have not initialized all the other 59 3390-3 and CP is getting upset. I am in the process of using ICKDSF to do a quick initialize putting a volume seriam number on these DASDs and try again. Wish me luck. This is a classic case of "lack of planning and totally reflected on me" ^e^ ... Thanks again. ..RolandGeorge Haddad <[EMAIL PROTECTED]> wrote: I believe I mis-spoke in my prev email, it is the CUNUMBR field on the CNTLUNIT macro that we use to re-define our CHPIDs to "more desirable" numbers.With best regards,...Roland ChungSenior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)MAXC Consultants Inc.Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268)197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6** Life is short. Stop once in a while and smell the roses. **
Re: IOCP for MP2003-204
I believe I mis-spoke in my prev email, it is the CUNUMBR field on the CNTLUNIT macro that we use to re-define our CHPIDs to "more desirable" numbers.
Re: IOCP for MP2003-204
ROland, sorry I could not get back to "the list" on Friday with our IOCP. While it is much less populated than the other posters' examples, ours *may* help with your console problems if you have a similar config. We have a 3174 attached to one of the MP2003 bus&tag channels. However, we've redefined the Channels to be different from the Paths via the UNITADDR parm on the CNTRLUNIT stmts. THe bus&tag channels are at paths 40-45 on our MP2003-205, but to match a config from a previous machine, we redefined them so that our 3174 appears as Channel 00, our Tapes are on Channel 05 (and formerly Channel 15), and our now-de-installed external DASD were on Channels 0B/0F. I'll append the IOCP source file at the end of your quote. It's worked for us since our initial migration back in 1999. Hope it helps. Roland P. Chung wrote: Hello All, thanks to all who responded. After hours of struggling, I manage to set up a IOCDS which I was able to get at the tape drives, DASDs and 3174. IPLed the standalone ICKDSF and DDR. I was very happy to be able to restore all 5 CP OWNED volumes. Came to the monent of truth IPL'ed VM hit the terminal... nothing... After spent hours investigating and trial many different address on the 3174, I only can figure out that VM can't get at the 3174 because in the SYSTEM CONFIG file, it says: Operator_Consoles 001F 0020 0021 0022 0023 Emergency_Message_Consoles 0020 0021 0022 0023 And in MP2003 world, I think there are no channel 0 anymore and there re no good old 01F(the integrated console) hangs on that channel either. I think the address (at least the UU) has been hardcoded as 40-5F on the 3174 controler. I was very tire my brian can only think of a few solutions: 1) find an IBM "Productivity Centre" near Washinging, DC (if there are such thing in US!), restore the 5 pack VM system, IPL it and fix the SYSTEM CONFIG to include 040 - 043 (the address on that 3174); Backup the 230RES, restore it back here and I should be in business 2) reconfigure the 3174 to start the UU from 20 - well, the Utility and a backup disk are there only thing I need is a manual. Anyone has a LINK I can get a softcopy? 3) get a zVM DVD? How and where? Anyone has a better idea on how to resolve this problem? TIA MSU's MP2003-205 IOCP: -- ID MSG1='2003VM3 IOCP FOR MP2003 RUNNING MSUVM3', * MSG2='Created 04/14/99 GJH', * SYSTEM=(2003,1) *IOCP = *IOCP IOCDS for 2003-205 running MSUVM3 *IOCP *IOCP 09/26/91 GJH: Created (from original 9221 IOCDS via export) *IOCP 09/30/91 GJH: Add Def for 7171 (300-33F) *IOCP 05/07/93 GJH: Add Def for 3480 (590-59F) *IOCP 09/09/93 GJH: Add Def for BTI (380-38F) *IOCP 12/06/94 GJH: Add Def for 9336 (D40-D5F) *IOCP 01/04/95 GJH: Remove 9332's, define 9336's on channel C *IOCP 07/18/96 GJH: Remove extraneous 9336 defs *IOCP 10/03/97 GJH: Define 3990/3390s (B40/F40) *IOCP 02/02/98 GJH: Add defs for MP2003 internal devices *IOCP 01/07/99 GJH: Add defs for Memorex Cart Tape drives *IOCP *IOCP *IOCP = *IOCP *IOCP MP2003 Internal Devices *IOCP CHPID PATH=(5A),TYPE=ISD CHPID PATH=(5C),TYPE=OSA CHPID PATH=(5E),TYPE=ISD *IOCP *IOCP Parallel (Bus & Tag) Channels: *IOCP CHPID PATH=(40),TYPE=BL CHPID PATH=(41),TYPE=BL CHPID PATH=(42),TYPE=BL CHPID PATH=(44),TYPE=BL
Re: IOCP for MP2003-204
Hi Roland, There are two places you must specify the console address. First off, you have to tell the hardware. That is what you are seeing on the Support Element console. For the IPL address, you use your dasd device address. For the Loadparm, just enter the device address of the terminal you want to use for the console. IPL the processor. SAPL should come up on the device you entered in the Loadparm field. At that point you can enter cons= to tell VM where to find the console, and continue with the VM IPL. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Roland P. Chung Sent: June 19, 2006 09:50 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IOCP for MP2003-204 Hi All, thanks for all your responses. How could I forget the SAPL. Must be getting old The customer is still using VM/ESA 2.30... I don't know if the SAPL would take the LOADPARM. Anyway, the application runing on the MP2003-204 allows a place to put in a load address and a load parameter. However, it only allows 8 characters in this load parameter field, but NO special characters allows, like the = sign... RRRrr.. There are no "intergrated console support" in this beast either Do you have other suggestions? TIA Regards, ...Roland Kris Buelens <[EMAIL PROTECTED]> wrote: In some z/VM release, new possibilities have been added in the area of console address override. I don't know which release, but it surely already work in z/VM 4.4 Here's a summary of what you now can do - LOADPARM rdev --> starts SAPL on "rdev", there you can enter CONS=rdev to tell CP where to go and load CP - LOADPARM CONSrdev -> SAPL directly loads CP and passes CONS=rdev As rdev one can also specify SYSG to indicate the "integrated 3270 CONSOLE", very easy but first you must drag a "3270 console" icon on the icon of the LPAR in which you want to load VM. Both SAPLand CP support this console (z/OS does not), so the LOADPARM can be SYSG or CONSSYSG Similar, there is SYSC, the integrated linemode console, not supported by SAPL, so you can also enter LOADPARM CONSSYSC to directly load CP and instruct it to got to that linemode terminal. Kris, IBM Belgium, VM customer support The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking of any action in reliance upon, this information by persons or entities other than the intended recipient or delegate is strictly prohibited. If you received this in error, please contact the sender and delete the material from any computer. The integrity and security of this message cannot by guaranteed on the Internet. The Sender accepts no liability for the content of this e-mail, or for the consequences of any actions taken on basis of the information provided. The recipient should check this e-mail and any attachments for the presence of viruses. The sender accepts no liability for any damage caused by any virus transmitted by this e-mail. This disclaimer is the property of the TTC and must not be altered or circumvented in any manner.
Re: IOCP for MP2003-204
Hi All, thanks for all your responses. How could I forget the SAPL. Must be getting old The customer is still using VM/ESA 2.30... I don't know if the SAPL would take the LOADPARM. Anyway, the application runing on the MP2003-204 allows a place to put in a load address and a load parameter. However, it only allows 8 characters in this load parameter field, but NO special characters allows, like the = sign... RRRrr.. There are no "intergrated console support" in this beast either Do you have other suggestions? TIA Regards, ...RolandKris Buelens <[EMAIL PROTECTED]> wrote: In some z/VM release, new possibilities have been added in the area of console address override. I don't know which release, but it surely already work in z/VM 4.4 Here's a summary of what you now can do - LOADPARM rdev --> starts SAPL on "rdev", there you can enter CONS=rdev to tell CP where to go and load CP - LOADPARM CONSrdev -> SAPL directly loads CP and passes CONS=rdev As rdev one can also specify SYSG to indicate the "integrated 3270 CONSOLE", very easy but first you must drag a "3270 console" icon on the icon of the LPAR in which you want to load VM. Both SAPLand CP support this console (z/OS does not), so the LOADPARM can be SYSG or CONSSYSG Similar, there is SYSC, the integrated linemode console, not supported by SAPL, so you can also enter LOADPARM CONSSYSC to directly load CP and instruct it to got to that linemode terminal. Kris,IBM Belgium, VM customer support
Re: IOCP for MP2003-204
The use of SYSG as the console device is both hardware and software dependent. So you need both a SAPL utility that supports SYSG, but also a processor. I think the hardware level set for SYSG is maybe z/890 / z/990, so it's unlikely the box Roland is using supports SYSG. However, as others have said, you should certainly be able to supply one of your valid 3174 addresses via the LOADPARM override to get the system IPL'd. JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Kris BuelensSent: Monday, June 19, 2006 04:33 AMTo: IBMVM@LISTSERV.UARK.EDUSubject: Re: IOCP for MP2003-204 In some z/VM release, new possibilities have been added in the area of console address override. I don't know which release, but it surely already work in z/VM 4.4 Here's a summary of what you now can do - LOADPARM rdev --> starts SAPL on "rdev", there you can enter CONS=rdev to tell CP where to go and load CP - LOADPARM CONSrdev -> SAPL directly loads CP and passes CONS=rdev As rdev one can also specify SYSG to indicate the "integrated 3270 CONSOLE", very easy but first you must drag a "3270 console" icon on the icon of the LPAR in which you want to load VM. Both SAPLand CP support this console (z/OS does not), so the LOADPARM can be SYSG or CONSSYSG Similar, there is SYSC, the integrated linemode console, not supported by SAPL, so you can also enter LOADPARM CONSSYSC to directly load CP and instruct it to got to that linemode terminal. Kris,IBM Belgium, VM customer support
Re: IOCP for MP2003-204
In some z/VM release, new possibilities have been added in the area of console address override. I don't know which release, but it surely already work in z/VM 4.4 Here's a summary of what you now can do - LOADPARM rdev --> starts SAPL on "rdev", there you can enter CONS=rdev to tell CP where to go and load CP - LOADPARM CONSrdev -> SAPL directly loads CP and passes CONS=rdev As rdev one can also specify SYSG to indicate the "integrated 3270 CONSOLE", very easy but first you must drag a "3270 console" icon on the icon of the LPAR in which you want to load VM. Both SAPLand CP support this console (z/OS does not), so the LOADPARM can be SYSG or CONSSYSG Similar, there is SYSC, the integrated linemode console, not supported by SAPL, so you can also enter LOADPARM CONSSYSC to directly load CP and instruct it to got to that linemode terminal. Kris, IBM Belgium, VM customer support
Re: IOCP for MP2003-204
On 19 Jun 2006 at 1:16, Roland P. Chung wrote: > Came to the monent of truth IPL'ed VM hit the > terminal... nothing... > > After spent hours investigating and trial many different > address on the 3174, I only can figure out that VM can't > get at the 3174 because in the SYSTEM CONFIG file, it says: > > Operator_Consoles 001F 0020 0021 0022 0023 > Emergency_Message_Consoles 0020 0021 0022 0023 Isn't the VM IPL volume initialized with the SAPL? The Stand Alone Program Loader screen should come up on the terminal device supplied as the IPL Loadparm value, regardless of the contents of the SYSTEM CONFIG. (Since SAPL is *not* VM, it does not rely on the SYSTEM CONFIG file, it just "boots" VM). So.. are you using the correct value as the load parameter? Once you have the SAPL screen, you can override the console values in the SYSTEM CONFIG by typing: CONS=123 (or whatever valid address you have there) in the "parameters" section below the horizontal line on the screen. Then, when you hit PF10, VM should initialize using "123" as its IPL console. Good luck! Shimon
Re: IOCP for MP2003-204
On 6/19/06, Roland P. Chung <[EMAIL PROTECTED]> wrote: Came to the monent of truth IPL'ed VM hit the terminal... nothing... So you got a disabled wait or just sitting there with enabled wait? Did you use the LOADPARM to direct SAPL to your console and did it come up there? As far as I recall the cons= parameter on the SAPL options implies the set rdevice for it, so that should work for you. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
Re: IOCP for MP2003-204
Hello All, thanks to all who responded. After hours of struggling, I manage to set up a IOCDS which I was able to get at the tape drives, DASDs and 3174. IPLed the standalone ICKDSF and DDR. I was very happy to be able to restore all 5 CP OWNED volumes. Came to the monent of truth IPL'ed VM hit the terminal... nothing... After spent hours investigating and trial many different address on the 3174, I only can figure out that VM can't get at the 3174 because in the SYSTEM CONFIG file, it says: Operator_Consoles 001F 0020 0021 0022 0023 Emergency_Message_Consoles 0020 0021 0022 0023 And in MP2003 world, I think there are no channel 0 anymore and there re no good old 01F(the integrated console) hangs on that channel either. I think the address (at least the UU) has been hardcoded as 40-5F on the 3174 controler. I was very tire my brian can only think of a few solutions: 1) find an IBM "Productivity Centre" near Washinging, DC (if there are such thing in US!), restore the 5 pack VM system, IPL it and fix the SYSTEM CONFIG to include 040 - 043 (the address on that 3174); Backup the 230RES, restore it back here and I should be in business 2) reconfigure the 3174 to start the UU from 20 - well, the Utility and a backup disk are there only thing I need is a manual. Anyone has a LINK I can get a softcopy? 3) get a zVM DVD? How and where? Anyone has a better idea on how to resolve this problem? TIA Regards, ...Roland --- Alan Altmark <[EMAIL PROTECTED]> wrote: > On Friday, 06/16/2006 at 09:46 AST, George Haddad > <[EMAIL PROTECTED]> wrote: > > Our 2003-205 can be IMLed to do Dynamic I/O. We never > did implement that > > feature --- we just never made many I/O changes over > the yrs -- so I > > don't know if that negates the need for an inital IOCDS > load or not. > > No, it doesn't. To IPL CP you have to IPL *something*. > That *something* > must be in the active I/O configuration. You need a tape > drive and enough > dasd volumes to restore a basic VM system, plus a > console. > > This is the nice thing about having an emergency 1-pack > micro-system. > Sysres, paging, spooling, a directory, OPERATOR and > MAINT, DDR, IOCP, all > on one volume, with the console pointing to the > integrated console (on > modern machines, integrated 3270). Or, also on modern > machines, the > ability to IPL the z/VM DVD. > > IF you authorized the LPAR to perform dynamic I/O > operations and you have > dynamic I/O enabled in VM, then CP, once up, can start to > add chpids, > control units, and devices to the I/O config. > > Alan Altmark > z/VM Development > IBM Endicott >
Re: IOCP for MP2003-204
On Friday, 06/16/2006 at 09:46 AST, George Haddad <[EMAIL PROTECTED]> wrote: > Our 2003-205 can be IMLed to do Dynamic I/O. We never did implement that > feature --- we just never made many I/O changes over the yrs -- so I > don't know if that negates the need for an inital IOCDS load or not. No, it doesn't. To IPL CP you have to IPL *something*. That *something* must be in the active I/O configuration. You need a tape drive and enough dasd volumes to restore a basic VM system, plus a console. This is the nice thing about having an emergency 1-pack micro-system. Sysres, paging, spooling, a directory, OPERATOR and MAINT, DDR, IOCP, all on one volume, with the console pointing to the integrated console (on modern machines, integrated 3270). Or, also on modern machines, the ability to IPL the z/VM DVD. IF you authorized the LPAR to perform dynamic I/O operations and you have dynamic I/O enabled in VM, then CP, once up, can start to add chpids, control units, and devices to the I/O config. Alan Altmark z/VM Development IBM Endicott
Re: IOCP for MP2003-204
CP reads the hardware configuration by Store-SubChannel-ID. That ID must map to a device number. Using SubChannel-ID, CP can issue I/O to get device information like device type. Using device type, CP can decide what to do with the device. DASD: read its label. Terminal: write the logon logo. Etc. But it all starts with the hardware being properly defined. IOCDS. Gotta have it. Richard Corak It's been quite a while since I worked at that level but I didn't (don't) think that CP is going to be able to sense anything that isn't defined in the active IOCDS. It seems to me that was why I used to have to give a tape to the CE to load a basic IOCDS that would be enough to start with. I hope I'm wrong. Jim
Re: IOCP for MP2003-204
Hi George, it sounds good. I will look into that. Do you happen to have a copy of the IOCP source for your MP2003-205 handy. It would be greatly appreciated if you can post it or send me a copy for reference. Thanks a lot in advance. Regards, ...RolandGeorge Haddad <[EMAIL PROTECTED]> wrote: Our 2003-205 can be IMLed to do Dynamic I/O. We never did implement that feature --- we just never made many I/O changes over the yrs -- so I don't know if that negates the need for an inital IOCDS load or not.Jim Bohnsack wrote:> It's been quite a while since I worked at that level but I didn't > (don't) think that CP is going to be able to sense anything that isn't > defined in the active IOCDS. It seems to me that was why I used to > have to give a tape to the CE to load a basic IOCDS that would be > enough to start with.>> I hope I'm wrong.> Jim>> At 11:38 AM 6/15/2006, you wrote:>> --0-1955985212-1150385931=:22404>> Content-Type: text/plain; charset=iso-8859-1>> Content-Transfer-Encoding: 8bit Hi Peter, that is what I will do. Just talked to the hardware installer. No, he is not going to >> create a basic IOCP for us. But, he agreed to format the Shark for us >> to emulate 3390-3. He will also leave us a list on what CHPID the >> devices are connected to. I have managed to create a standalone IPLable tape with ICKDSF and >> DDR before they took down the Hitachi. I would format the needed >> DASDs and restore the CP OWNED volumns - 4 of them. Then I will try >> to IPL VM. At that stage, I can use all 6 tape drives to restore the >> other 60 DASDs. Hopefully, I can re-IPL to bring up the full VM system. Since CP would sense all the devices, I think I can use the >> DCPRDEVS utility to build a file of all real devices on the system. >> From there, I can build the final IOCS file and put it back to the >> service element using the IOCP command. Thanks for your suggestions. Regards, ...Roland
Re: IOCP for MP2003-204
Our 2003-205 can be IMLed to do Dynamic I/O. We never did implement that feature --- we just never made many I/O changes over the yrs -- so I don't know if that negates the need for an inital IOCDS load or not. Jim Bohnsack wrote: It's been quite a while since I worked at that level but I didn't (don't) think that CP is going to be able to sense anything that isn't defined in the active IOCDS. It seems to me that was why I used to have to give a tape to the CE to load a basic IOCDS that would be enough to start with. I hope I'm wrong. Jim At 11:38 AM 6/15/2006, you wrote: --0-1955985212-1150385931=:22404 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Peter, that is what I will do. Just talked to the hardware installer. No, he is not going to create a basic IOCP for us. But, he agreed to format the Shark for us to emulate 3390-3. He will also leave us a list on what CHPID the devices are connected to. I have managed to create a standalone IPLable tape with ICKDSF and DDR before they took down the Hitachi. I would format the needed DASDs and restore the CP OWNED volumns - 4 of them. Then I will try to IPL VM. At that stage, I can use all 6 tape drives to restore the other 60 DASDs. Hopefully, I can re-IPL to bring up the full VM system. Since CP would sense all the devices, I think I can use the DCPRDEVS utility to build a file of all real devices on the system. From there, I can build the final IOCS file and put it back to the service element using the IOCP command. Thanks for your suggestions. Regards, ...Roland
Re: IOCP for MP2003-204
It's been quite a while since I worked at that level but I didn't (don't) think that CP is going to be able to sense anything that isn't defined in the active IOCDS. It seems to me that was why I used to have to give a tape to the CE to load a basic IOCDS that would be enough to start with. I hope I'm wrong. Jim At 11:38 AM 6/15/2006, you wrote: --0-1955985212-1150385931=:22404 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Peter, that is what I will do. Just talked to the hardware installer. No, he is not going to create a basic IOCP for us. But, he agreed to format the Shark for us to emulate 3390-3. He will also leave us a list on what CHPID the devices are connected to. I have managed to create a standalone IPLable tape with ICKDSF and DDR before they took down the Hitachi. I would format the needed DASDs and restore the CP OWNED volumns - 4 of them. Then I will try to IPL VM. At that stage, I can use all 6 tape drives to restore the other 60 DASDs. Hopefully, I can re-IPL to bring up the full VM system. Since CP would sense all the devices, I think I can use the DCPRDEVS utility to build a file of all real devices on the system. From there, I can build the final IOCS file and put it back to the service element using the IOCP command. Thanks for your suggestions. Regards, ...Roland [EMAIL PROTECTED] wrote: Hi Roland, Well, if the 2003-204 is anything like our 2003-225, then you have some work to do. First, VM/ESA 2.3 should run just fine; we ran it for several years before upgrading to z/VM 3.1. You can forget the old IOCP from the Hitachi box, or any IOCP from another shop. The problem here is that the CHPID numbers on the 2003 start at x'40' and go up, with some skips (e.g. No x'4F'). Have your hardware guy cable up the equipment the way it makes most sense to him, and create a basic IOCP. I assume you are using the internal dasd. As per Rob van der Heij, have your hardware guy set them up as 3390-3. You will also get some small volumes in this configuration, watch out for them. They can be useful later, but will be a pain right now. IPL standalone ICKDSF from your backup tapes and format all the volumes. Use standalone DDR to restore your backups. Try IPLing your system residence volume when you have finished the restores. If you are lucky, and the customer used sensible VM configuration options, you should get at least OPERATOR up, and maybe the whole system. Peter snipped With best regards, ...Roland Chung Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) MAXC Consultants Inc. Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 ** Life is short. Stop once in a while and smell the roses. ** --0-1955985212-1150385931=:22404 Content-Type: text/html; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Hi Peter, that is what I will do. Just talked to the hardware installer. No, he is not going to create a basic IOCP for us. But, he agreed to format the Shark for us to emulate 3390-3. He will also leave us a list on what CHPID the devices are connected to. I have managed to create a standalone IPLable tape with ICKDSF and DDR before they took down the Hitachi. I would format the needed DASDs and restore the CP OWNED volumns - 4 of them. Then I will try to IPL VM. At that stage, I can use all 6 tape drives to restore the other 60 DASDs. Hopefully, I can re-IPL to bring up the full VM system. Since CP would sense all the devices, I think I can use the DCPRDEVS utility to build a file of all real devices on the system. From there, I can build the final IOCS file and put it back to the service element using the IOCP command. Thanks for your suggestions. Regards, ...Roland [EMAIL PROTECTED] wrote: Hi Roland,Well, if the 2003-204 is anything like our 2003-225, then you have somework to do. First, VM/ESA 2.3 should run just fine; we ran it forseveral years before upgrading to z/VM 3.1. You can forget the old IOCPfrom the Hitachi box, or any IOCP from another shop. The problem here is that the CHPID numbers on the 2003 start at x'40'and go up, with some skips (e.g. No x'4F'). Have your hardware guy cableup the equipment the way it makes most sense to him, and create a basicIOCP. I assume you are using the internal dasd. As per Rob van der Heij, haveyour hardware guy set them up as 3390-3. You will also get some smallvolumes in this configuration, watch out for them. They can be usefullater, but will be a pain right now. IPL standalone ICKDSF from your backup tapes and format all the volumes.Use standalone DDR to restore your backups. Try IPLing your systemresidence volume when you have finished the restores. If you are lucky,and the customer used sensible VM configuration options, you should getat least OPERATOR up, and maybe the whole system.Peter snipped With best regards,...Roland ChungSenior Techn
Re: IOCP for MP2003-204
Hi Peter, that is what I will do. Just talked to the hardware installer. No, he is not going to create a basic IOCP for us. But, he agreed to format the Shark for us to emulate 3390-3. He will also leave us a list on what CHPID the devices are connected to. I have managed to create a standalone IPLable tape with ICKDSF and DDR before they took down the Hitachi. I would format the needed DASDs and restore the CP OWNED volumns - 4 of them. Then I will try to IPL VM. At that stage, I can use all 6 tape drives to restore the other 60 DASDs. Hopefully, I can re-IPL to bring up the full VM system. Since CP would sense all the devices, I think I can use the DCPRDEVS utility to build a file of all real devices on the system. From there, I can build the final IOCS file and put it back to the service element using the IOCP command. Thanks for your suggestions. Regards, ...Roland [EMAIL PROTECTED] wrote: Hi Roland,Well, if the 2003-204 is anything like our 2003-225, then you have somework to do. First, VM/ESA 2.3 should run just fine; we ran it forseveral years before upgrading to z/VM 3.1. You can forget the old IOCPfrom the Hitachi box, or any IOCP from another shop. The problem here is that the CHPID numbers on the 2003 start at x'40'and go up, with some skips (e.g. No x'4F'). Have your hardware guy cableup the equipment the way it makes most sense to him, and create a basicIOCP. I assume you are using the internal dasd. As per Rob van der Heij, haveyour hardware guy set them up as 3390-3. You will also get some smallvolumes in this configuration, watch out for them. They can be usefullater, but will be a pain right now. IPL standalone ICKDSF from your backup tapes and format all the volumes.Use standalone DDR to restore your backups. Try IPLing your systemresidence volume when you have finished the restores. If you are lucky,and the customer used sensible VM configuration options, you should getat least OPERATOR up, and maybe the whole system.Peter snipped With best regards,...Roland ChungSenior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)MAXC Consultants Inc.Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268)197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6** Life is short. Stop once in a while and smell the roses. **
Re: IOCP for MP2003-204
Hello Aria, thanks. It helps a lot. Just came out from a phone conversion with the hardware installor. He is going to provide a list on what CHPID he had all the devices connected to. Since the Shark is going to connect to the ESCON channel, he said it will on CHPID 40,41,42,43,48,49,4A,4B. He will format it to 3390-3 for us. I guess I have to get the list and try to come up with a IOCP. The IOCPs you provided are an excellent reference. Thanks a lot again. Regards, ...Roland Aria Bamdad <[EMAIL PROTECTED]> wrote: Roland,Without knowing more about CHPID numbers and addresses, we can't provideyou with an IOCP that will work on your system. This is somethingthat has to be taylored to each machine.Below, I have included two IOCP files. One is a fragment of a MP2003IOCP, the other is from an MP3000. The machine type doesn't matter much.You can look at these and build an IOCP for your machine. The OSAcards in these two IOCPs are for an ethernet card but you have an TRcard.Hope this helps.Aria snipped ---With best regards,...Roland ChungSenior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM)MAXC Consultants Inc.Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268)197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6** Life is short. Stop once in a while and smell the roses. **
Re: IOCP for MP2003-204
I don’t generally like HCD, but another option (if you have another VM system accessible to you) would be to use HCD and the HCM GUI to define the configuration and then have HCD generate a IOCP deck. HCM still understands machines as old as the MP2K, and it can still generate IOCP decks with help from the HCD widget. David Boyes Sine Nomine Associates
Re: IOCP for MP2003-204
Hi Roland, Well, if the 2003-204 is anything like our 2003-225, then you have some work to do. First, VM/ESA 2.3 should run just fine; we ran it for several years before upgrading to z/VM 3.1. You can forget the old IOCP from the Hitachi box, or any IOCP from another shop. The problem here is that the CHPID numbers on the 2003 start at x'40' and go up, with some skips (e.g. No x'4F'). Have your hardware guy cable up the equipment the way it makes most sense to him, and create a basic IOCP. I assume you are using the internal dasd. As per Rob van der Heij, have your hardware guy set them up as 3390-3. You will also get some small volumes in this configuration, watch out for them. They can be useful later, but will be a pain right now. IPL standalone ICKDSF from your backup tapes and format all the volumes. Use standalone DDR to restore your backups. Try IPLing your system residence volume when you have finished the restores. If you are lucky, and the customer used sensible VM configuration options, you should get at least OPERATOR up, and maybe the whole system. Peter -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Roland P. Chung Sent: June 15, 2006 07:04 To: IBMVM@LISTSERV.UARK.EDU Subject: Re: IOCP for MP2003-204 Well, Rich, the Hitachi is out the door already. I hope the computer room manager would have a picture of the old machine configuration showing how the devices are connected to the Hitachi. With that, the installer can put a basic IOCP on the MP2003-204's storage element. As I know of on the Hitachi: DASD are on 200-23F Tapes are on 320 to 32F. Good luck to me! Regards, ...Roland --- Rich Smrcina <[EMAIL PROTECTED]> wrote: > That is going to be next to impossible without knowing > the CHPID numbers > and device numbers that they need. It's time to > reconnect the Hitachi box. > > Roland P. Chung wrote: > > Hello Listers, please help! I've been parachuted into > the > > middle of this. *SIGH* > > > > The client is migrating from a Hitachi EX-22 to a > > MP2003-204. The operating system is VM/ESA 2.30. Before > > they took down the old system , we did not make a copy > of > > the IOCP. The only thing we've managed to do is DDR > copied > > all 64 3390-3 DASDs. > > > > Could anyone has an IOCP similiar to the MP2003 system > that > > I can borrow. The new system's configuration is as > follow: > > > > CPU > > > > 15 CEC/Cage Airflow cards (0012) > > 1 External HMC/SE(0015) > > 1 204 1-Way Processor(0603) > > 1 No Crypto Hardware (0808) > > 2 4 port parallel cards (2304) > > 2 ESCON Channel (2313) > > 1 FIBBAC Card(2338) > > 1 1024 MN Memory Card(3024) > > 1 Token Ring (5201) > > 1 Small Console Display (6090) > > 1 4.8M 3 Phase - US (8887) > > 1 Northern Hemisphere(9930) > > > > Plus devices from the old system > > > > IBM 3490 Tape Systems > > 3490E A10 Controller > > 3490E B40 w/4 Tape Transports w/Autoloaders > > 3490E B20 w/2 Tape Transports w/Autoloaders > > > > IBM 4245/12 Printer > > > > IBM 3174/1L Communications Controller (coax > connections) > > > > IBM 3172/3 Communications Controller (Ethernet > connections) > > > > DASD > > > > 4 36.4gb 8 paks (2123) > > 4 ESCON Channels > > 8 GB cache > > * to be configured as 3390-3 > > > > Thanks a lot in advance. > > > > > > > > With best regards, > > > > ...Roland Chung > > Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) > > MAXC Consultants Inc. > > Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) > > 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 > > > > ** Life is short. Stop once in a while and smell the > roses. ** > > > > -- > Rich Smrcina > VM Assist, Inc. > Main: (262)392-2026 > Cell: (414)491-6001 > Ans Service: (360)715-2467 > rich.smrcina at vmassist.com > > Catch the WAVV! http://www.wavv.org > WAVV 2007 - Green Bay, WI - May 18-22, 2007 > With best regards, ...Roland Chung Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) MAXC Consultants Inc. Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 ** Life is short. Stop once in a while and smell the roses. ** The information transmitted is intended only for
Re: IOCP for MP2003-204
Roland,
Without knowing more about CHPID numbers and addresses, we can't provide
you with an IOCP that will work on your system. This is something
that has to be taylored to each machine.
Below, I have included two IOCP files. One is a fragment of a MP2003
IOCP, the other is from an MP3000. The machine type doesn't matter much.
You can look at these and build an IOCP for your machine. The OSA
cards in these two IOCPs are for an ethernet card but you have an TR
card.
Hope this helps.
Aria
-
ID MSG1='MULTIPRISE 20003',SYSTEM=(2003,1)
CHPIDPATH=((00)),TYPE=OSA
CHPIDPATH=((08)),TYPE=BL
CHPIDPATH=((09)),TYPE=BL
CHPIDPATH=((0A)),TYPE=BL
CHPIDPATH=((10)),TYPE=BL
CHPIDPATH=((11)),TYPE=BL
CHPIDPATH=((12)),TYPE=BL
CHPIDPATH=((14)),TYPE=BL
CHPIDPATH=((15)),TYPE=BL
CHPIDPATH=((16)),TYPE=BL
CHPIDPATH=((18)),TYPE=BL
CHPIDPATH=((19)),TYPE=BL
CHPIDPATH=((1A)),TYPE=BL
*
* MEMOREX 5450/1 TAPE DRIVE
*
CNTLUNIT CUNUMBR=510,PATH=18,SHARED=N,UNIT=3480,X
UNITADD=((10,16)),PROTOCL=S
IODEVICE ADDRESS=(510,02),CUNUMBR=510,UNIT=3480
*
* 3174 CONTROL UNIT
*
CNTLUNIT CUNUMBR=000,PATH=14,SHARED=N,UNIT=3174,X
UNITADD=((00,32)),PROTOCL=D
IODEVICE ADDRESS=(000,32),CUNUMBR=000,UNIT=3278
*
*IBM 3380-CJ2
*
CNTLUNIT CUNUMBR=B20,PATH=10,SHARED=N,UNIT=3880,X
UNITADD=((20,16)),PROTOCL=S
IODEVICE ADDRESS=(B20,16),CUNUMBR=(B20),UNIT=3380
*
*OSA-2
*
CNTLUNIT CUNUMBR=3F0,PATH=00,UNIT=OSA
IODEVICE ADDRESS=(3F0,4),CUNUMBR=(3F0),UNIT=OSA,UNITADD=00
*IOCP END
-
-
ID MSG1='20040508',SYSTEM=(7060,1), X
TOK=('VM-TOKEN',F0F161F0F361F0F4F1F27AF0F57AF0F240404040X
,,'05/09/04','00:05:50','','')
CHPIDPATH=(00),TYPE=CNC
CHPIDPATH=(01),TYPE=CNC
CHPIDPATH=(04),TYPE=CNC
CHPIDPATH=(05),TYPE=CNC
CHPIDPATH=(06),TYPE=CNC
CHPIDPATH=(07),TYPE=CNC
CHPIDPATH=(08),TYPE=BL
CHPIDPATH=(09),TYPE=BL
CHPIDPATH=(0A),TYPE=BL
CHPIDPATH=(0B),TYPE=BL
CHPIDPATH=(0C),TYPE=BL
CHPIDPATH=(0D),TYPE=BL
CHPIDPATH=(0E),TYPE=BL
CHPIDPATH=(0F),TYPE=BL
CHPIDPATH=(10),TYPE=BL
CHPIDPATH=(11),TYPE=BL
CHPIDPATH=(12),TYPE=BL
CHPIDPATH=(13),TYPE=BL
CHPIDPATH=(1E),TYPE=CNC
CHPIDPATH=(1F),TYPE=CNC
CHPIDPATH=(FC),TYPE=EIO
*
* 3174 CONTROL UNIT
* CHPID 08
*
CNTLUNIT CUNUMBR=000,PATH=08,SHARED=N,UNIT=3174,X
UNITADD=((00,32)),PROTOCL=D
IODEVICE ADDRESS=(000,32),CUNUMBR=000,UNIT=3278
*
*4245 PRINTER
* CHPID 08
*
CNTLUNIT CUNUMBR=070,PATH=08,SHARED=N,UNIT=4245,X
UNITADD=((70,08)),PROTOCL=D
IODEVICE ADDRESS=(077,1),CUNUMBR=070,UNIT=4245
*
* 3174 CONTROL UNIT
* CHPID 11
*
CNTLUNIT CUNUMBR=400,PATH=11,SHARED=N,UNIT=3174,X
UNITADD=((00,32)),PROTOCL=D
IODEVICE ADDRESS=(400,32),CUNUMBR=400,UNIT=3278
*
* MEMOREX 3281/8 TAPE DRIVE
* CHPID 0B
*
CNTLUNIT CUNUMBR=500,PATH=0B,SHARED=Y,UNIT=3803,X
UNITADD=((00,08)),PROTOCL=D
IODEVICE ADDRESS=(500,02),CUNUMBR=500,UNIT=3420
*
* MEMOREX 5450/1 TAPE DRIVE
* CHPID 0B
Re: IOCP for MP2003-204
On 6/15/06, Rich Smrcina <[EMAIL PROTECTED]> wrote: That is going to be next to impossible without knowing the CHPID numbers and device numbers that they need. It's time to reconnect the Hitachi box. Impossible? Wasn't that removed with z/VM 5.2 ? Ah, well... VM/ESA The way I would consider to move forward: 1. Configure the disk space for 3390-3 models 2. Define an IOCP to map disk and tape at whatever addreass you recall 3. Install a small VM system to do your restores 4. If you don't know what volumes are on what tapes you need to restore them all (the starter system takes 2 packs but you don't need to have the page packs already) 5. Look through the volumes and find your IPL pack and IPL the thing 2nd level 6. Find the source directory somewhere (if you really can not find it, kdirect comes to mind) 7. Maybe your original IOCP source is somewhere on the MAINT disks, or some CE-type userid. Otherwise go through directory and some config files to learn where devices were. Rob --
Re: IOCP for MP2003-204
Does the Hitachi box have a way to copy the IOCP (or IOCDS) to a diskette or print it out rather than hooking the equipment back up? Steve G. Rich Smrcina <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System 06/14/2006 09:56 PM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: IOCP for MP2003-204 That is going to be next to impossible without knowing the CHPID numbers and device numbers that they need. It's time to reconnect the Hitachi box. Roland P. Chung wrote: > Hello Listers, please help! I've been parachuted into the > middle of this. *SIGH* > > The client is migrating from a Hitachi EX-22 to a > MP2003-204. The operating system is VM/ESA 2.30. Before > they took down the old system , we did not make a copy of > the IOCP. The only thing we've managed to do is DDR copied > all 64 3390-3 DASDs. > > Could anyone has an IOCP similiar to the MP2003 system that > I can borrow. The new system's configuration is as follow: > > CPU > > 15 CEC/Cage Airflow cards (0012) > 1 External HMC/SE (0015) > 1 204 1-Way Processor (0603) > 1 No Crypto Hardware (0808) > 2 4 port parallel cards (2304) > 2 ESCON Channel (2313) > 1 FIBBAC Card (2338) > 1 1024 MN Memory Card (3024) > 1 Token Ring (5201) > 1 Small Console Display (6090) > 1 4.8M 3 Phase - US (8887) > 1 Northern Hemisphere (9930) > > Plus devices from the old system > > IBM 3490 Tape Systems > 3490E A10 Controller > 3490E B40 w/4 Tape Transports w/Autoloaders > 3490E B20 w/2 Tape Transports w/Autoloaders > > IBM 4245/12 Printer > > IBM 3174/1L Communications Controller (coax connections) > > IBM 3172/3 Communications Controller (Ethernet connections) > > DASD > > 4 36.4gb 8 paks (2123) > 4 ESCON Channels > 8 GB cache > * to be configured as 3390-3 > > Thanks a lot in advance. > > > > With best regards, > > ...Roland Chung > Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) > MAXC Consultants Inc. > Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) > 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 > > ** Life is short. Stop once in a while and smell the roses. ** > -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
Re: IOCP for MP2003-204
Well, Rich, the Hitachi is out the door already. I hope the computer room manager would have a picture of the old machine configuration showing how the devices are connected to the Hitachi. With that, the installer can put a basic IOCP on the MP2003-204's storage element. As I know of on the Hitachi: DASD are on 200-23F Tapes are on 320 to 32F. Good luck to me! Regards, ...Roland --- Rich Smrcina <[EMAIL PROTECTED]> wrote: > That is going to be next to impossible without knowing > the CHPID numbers > and device numbers that they need. It's time to > reconnect the Hitachi box. > > Roland P. Chung wrote: > > Hello Listers, please help! I've been parachuted into > the > > middle of this. *SIGH* > > > > The client is migrating from a Hitachi EX-22 to a > > MP2003-204. The operating system is VM/ESA 2.30. Before > > they took down the old system , we did not make a copy > of > > the IOCP. The only thing we've managed to do is DDR > copied > > all 64 3390-3 DASDs. > > > > Could anyone has an IOCP similiar to the MP2003 system > that > > I can borrow. The new system's configuration is as > follow: > > > > CPU > > > > 15 CEC/Cage Airflow cards (0012) > > 1 External HMC/SE(0015) > > 1 204 1-Way Processor(0603) > > 1 No Crypto Hardware (0808) > > 2 4 port parallel cards (2304) > > 2 ESCON Channel (2313) > > 1 FIBBAC Card(2338) > > 1 1024 MN Memory Card(3024) > > 1 Token Ring (5201) > > 1 Small Console Display (6090) > > 1 4.8M 3 Phase - US (8887) > > 1 Northern Hemisphere(9930) > > > > Plus devices from the old system > > > > IBM 3490 Tape Systems > > 3490E A10 Controller > > 3490E B40 w/4 Tape Transports w/Autoloaders > > 3490E B20 w/2 Tape Transports w/Autoloaders > > > > IBM 4245/12 Printer > > > > IBM 3174/1L Communications Controller (coax > connections) > > > > IBM 3172/3 Communications Controller (Ethernet > connections) > > > > DASD > > > > 4 36.4gb 8 paks (2123) > > 4 ESCON Channels > > 8 GB cache > > * to be configured as 3390-3 > > > > Thanks a lot in advance. > > > > > > > > With best regards, > > > > ...Roland Chung > > Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) > > MAXC Consultants Inc. > > Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) > > 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 > > > > ** Life is short. Stop once in a while and smell the > roses. ** > > > > -- > Rich Smrcina > VM Assist, Inc. > Main: (262)392-2026 > Cell: (414)491-6001 > Ans Service: (360)715-2467 > rich.smrcina at vmassist.com > > Catch the WAVV! http://www.wavv.org > WAVV 2007 - Green Bay, WI - May 18-22, 2007 > With best regards, ...Roland Chung Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) MAXC Consultants Inc. Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 ** Life is short. Stop once in a while and smell the roses. **
Re: IOCP for MP2003-204
That is going to be next to impossible without knowing the CHPID numbers and device numbers that they need. It's time to reconnect the Hitachi box. Roland P. Chung wrote: Hello Listers, please help! I've been parachuted into the middle of this. *SIGH* The client is migrating from a Hitachi EX-22 to a MP2003-204. The operating system is VM/ESA 2.30. Before they took down the old system , we did not make a copy of the IOCP. The only thing we've managed to do is DDR copied all 64 3390-3 DASDs. Could anyone has an IOCP similiar to the MP2003 system that I can borrow. The new system's configuration is as follow: CPU 15 CEC/Cage Airflow cards (0012) 1 External HMC/SE(0015) 1 204 1-Way Processor(0603) 1 No Crypto Hardware (0808) 2 4 port parallel cards (2304) 2 ESCON Channel (2313) 1 FIBBAC Card(2338) 1 1024 MN Memory Card(3024) 1 Token Ring (5201) 1 Small Console Display (6090) 1 4.8M 3 Phase - US (8887) 1 Northern Hemisphere(9930) Plus devices from the old system IBM 3490 Tape Systems 3490E A10 Controller 3490E B40 w/4 Tape Transports w/Autoloaders 3490E B20 w/2 Tape Transports w/Autoloaders IBM 4245/12 Printer IBM 3174/1L Communications Controller (coax connections) IBM 3172/3 Communications Controller (Ethernet connections) DASD 4 36.4gb 8 paks (2123) 4 ESCON Channels 8 GB cache * to be configured as 3390-3 Thanks a lot in advance. With best regards, ...Roland Chung Senior Technical Specialist (S/390,VM/VSE,DB2/VSE&VM) MAXC Consultants Inc. Voice/Fax: 416-469-3280 (If busy, call: 416-469-2268) 197 Hastings Ave., Toronto, Ontario, Canada. M4L 2L6 ** Life is short. Stop once in a while and smell the roses. ** -- Rich Smrcina VM Assist, Inc. Main: (262)392-2026 Cell: (414)491-6001 Ans Service: (360)715-2467 rich.smrcina at vmassist.com Catch the WAVV! http://www.wavv.org WAVV 2007 - Green Bay, WI - May 18-22, 2007
