Re: CMS Levels
On Friday, 05/05/2006 at 03:05 MST, "Schuh, Richard" <[EMAIL PROTECTED]> wrote: > Thanks Jim. We are on top of the MAINT disks and CMS level. It is more the > relationship, if any, of SFS to NFS to TCP/IP levels that is of concern. There is no dependency between levels of SFS and NFS, nor between levels of NFS and the stack. Alan Altmark z/VM Development IBM Endicott
Re: CMS Levels
Thanks Jim. We are on top of the MAINT disks and CMS level. It is more the relationship, if any, of SFS to NFS to TCP/IP levels that is of concern. Big-bang seemed the only way to guarantee that we would be given the time to do the non-CP components. When we implemented the 4.4 CP, we were inundated with truly hot projects and never were able to find the time to do the rest. Regards, Richard Schuh -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Jim Bohnsack Sent: Friday, May 05, 2006 2:43 PM To: IBMVM@LISTSERV.UARK.EDU Subject:Re: CMS Levels I had a problem when I first went to z/VM 4.4 because the SFS serves were still pointing to the MAINT ??? disk which was at the z/VM 4.3 level, so if you run SFS with a 5.2 CMS, make sure that whichever of the MAINT disks they, be default, access are at the 5.2 level. My preference is to update a service at a time rather than doing a "big bang" type of update. Jim At 04:14 PM 5/5/2006, you wrote: >Tomorrow will be our next (last, we hope) attempt to move to 5.2. In the = >event that we should have to regress to our current system, I was = >wondering if it is possible and prudent to leave some of our servers at = >the CMS22 level. Specifically, is it necessary to fallback the SFS and = >NFS servers? We know that TCP/IP and all of its friends will need to = >revert to their former selves. Does the NFS machine have to match the = >level of TCP/IP? If so, does SFS have to degress to match? We are = >back-level with SFS and have a problem that is fixed in V5, so we really = >would like to leave SFS at the CMS22 level if we go back. > >We have been running CMS22 in most of our other service and several = >individual user machines (80+ users in all) for over a month with = >absolutely zero release-related problems. > >Regards, >Richard Schuh Jim Bohnsack Cornell Univ. (607) 255-1760
Re: CMS Levels
I had a problem when I first went to z/VM 4.4 because the SFS serves were still pointing to the MAINT ??? disk which was at the z/VM 4.3 level, so if you run SFS with a 5.2 CMS, make sure that whichever of the MAINT disks they, be default, access are at the 5.2 level. My preference is to update a service at a time rather than doing a "big bang" type of update. Jim At 04:14 PM 5/5/2006, you wrote: Tomorrow will be our next (last, we hope) attempt to move to 5.2. In the = event that we should have to regress to our current system, I was = wondering if it is possible and prudent to leave some of our servers at = the CMS22 level. Specifically, is it necessary to fallback the SFS and = NFS servers? We know that TCP/IP and all of its friends will need to = revert to their former selves. Does the NFS machine have to match the = level of TCP/IP? If so, does SFS have to degress to match? We are = back-level with SFS and have a problem that is fixed in V5, so we really = would like to leave SFS at the CMS22 level if we go back. We have been running CMS22 in most of our other service and several = individual user machines (80+ users in all) for over a month with = absolutely zero release-related problems. Regards, Richard Schuh Jim Bohnsack Cornell Univ. (607) 255-1760
Re: OT: German teddy bears
Lovely bears but they are not German but Dutch. Anyway, it IS just like V M, they keep on running and jumping. Berry.
Re: RMS and the C runtime library
Steve, the LE run time file names all start with either SCEE* or CEE* and are all located on the Y (19E) disk. The SCEERUN LOADLIB is the runtime library itself, I believe. DJ Steve Gentry wrote: Hello. Does anyone know what minidisk the LE code is on in VM 5.2? Specifically The C runtime library of LE Thanks. Steve G.
Re: Question about ISPFVM on z/VM V5R2
Craig, the method for defining and saving DCSS in VM hasn't changed in quite some time. The instructions in the ISPFVM Program Directory are almost certainly still valid. On ISPVM's 192 disk, there is an exec named ISPSAVE that does the actual build of the DCSS. so what you need to do is the following: 1) delete the old ISPDCSS DCSS (PURGE NSS .) 2) figure out where you want the new ISPDCSS to be in virtual storage, and define it there. (DEFSEG ISPDCSS .) 3) run the ISPSAVE exec with the right parms. Hope this is of some help. DJ Craig Dudley wrote: Dave, the returned error code (41) gives a hint...the CMS storage where the ISPF dcss needs to go is already being used by something else. My guest is that your CMS user ids on your new 5.2 system are significantly larger than they were on your old system. Try setting the virtual storage for the CMS guest down below the location of the ISPF dcss and see if that doesn't at least allow ISPF to start. Yeah - it looks like there are some conflicts. Here is a partial of a q nss all map: FILE FILENAME FILETYPE MINSIZE BEGPAG ENDPAG TYPE CL #USERS PARMREGS VMGROUP 0021 NLSGER DCSS N/A02000 020FF SR A 0 N/A N/A 0020 NLSKANJI DCSS N/A02000 020FF SR A 0 N/A N/A 0035 NLSUCENG DCSS N/A02000 020FF SR A 0 N/A N/A 0034 NLSAMENG DCSS N/A02000 020FF SR A 00012 N/A N/A 0049 ISPDCSS DCSS N/A02000 020FF SR A 0 N/A N/A So now I need to figure out how to move the ISPDCSS to a new location. Or move the NLS DCSS. Any ideas as to which is easier? I don't know how to adapt the VM/XA or VM/SP HPO instructions to the newer environment. Are there any more modern instructions for changing the ISPDCSS BEGPAG? -- Thanks Craig DJ Craig Dudley wrote: Hi, I am converting from a z/VM V3R1 system to a z/VM V5R2 system. I have ISPF VM V3R2 on my 3.1 system. I copied all the minidisks from the 3.1 system to the 5.2 system. I SPXTAPEd the ISPDCSS & SVM DCSS' from the 3.1 spool to the 5.2 spool. We XAUTOLOGed ISPVM on 5.2 and it came up without any errors on the console log. This was verified by logging onto ISPVM and running the PROFILE manually. When my user tries to invoke ISPF for VM, I get: DMSSLG332E No user additions were loaded RETURN CODE FROM SEGMENT MACRO (LOADSYS) IS 41, SEE YOUR SYTEM PROGRAMMER ISPF DCSS SEGMENT NOT LOADED 81 *-* 'ISPDCS ISPDCSS ISPVM 'arg string +++ RC(998) +++ With my 5.2 system I received a ISPF for VM V3R2 program directory but it seems to be written with VM/XA or VM/SP HPO in mind. So we are looking into the DMSSLG332E message. What we don't know is why the ISPDCS ISPDCSS ISPVM is failing. Please note that this is not ISPF/PDF, just ISPF. Any ideas would be appreciated. Thanks
CMS Levels
Tomorrow will be our next (last, we hope) attempt to move to 5.2. In the event that we should have to regress to our current system, I was wondering if it is possible and prudent to leave some of our servers at the CMS22 level. Specifically, is it necessary to fallback the SFS and NFS servers? We know that TCP/IP and all of its friends will need to revert to their former selves. Does the NFS machine have to match the level of TCP/IP? If so, does SFS have to degress to match? We are back-level with SFS and have a problem that is fixed in V5, so we really would like to leave SFS at the CMS22 level if we go back. We have been running CMS22 in most of our other service and several individual user machines (80+ users in all) for over a month with absolutely zero release-related problems. Regards, Richard Schuh
RMS and the C runtime library
Hello. Does anyone know what minidisk the LE code is on in VM 5.2? Specifically The C runtime library of LE Thanks. Steve G.
Re: zVM 5.1 Res Volume
Thank you. Cecelia Dusha -Original Message- From: Romanowski, John (OFT) [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 1:38 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume You said you DDR-ed the old 510RES to the new 510RES and reworked cyl 0 of the new 510RES; and you're running now using the old 510RES. So you can fix the new 510RES's cyl 0 from the VM system that's still running off the old 510RES, no need to IPL the new 510RES first with the NODIRECT option and try to fix it (easier to do it that way on a guest). First, To avoid issues of old 510RES's contents having diverged from new 510RES's, repeat your steps that DDR-ed the old to new 510RES, , CPFMTXA, etc. Then on MAINT, Get your latest CP directory in source file format as file USER DIRECT A (on userid VMXSYSAD do VMXBKP01 NOTAPE to create file USER DIRECT) The DIRECTORY statement in USER DIRECT says DIRECTORY ... ATTACH the new 510RES to MAINT at virtual addr Response from CP Q V should then say: DASD ON DASD R/W 510RES ... Then fix new 510RES's active-directory pointer in cyl 0 DIRECTXA USER DIRECT A (TEST DIRECTXA USER DIRECT A Will update the new 510RES object directory (DRCT area) and fix its cyl 0 active-directory pointer. You could also do this more safely from a class G userid to which you attach as and give the USER DIRECT A file. Then shutdown VM and re-ipl using the new fixed 510RES. VMSECURE's 191 file DIRECT STATEMNT, still has the old 510RES device address, , in it. You'll want to fix that file to change to . Alternative: don't ddr entire old 510RES to new, just run the DIRECTXA steps to fix new 510RES cyl 0 and rewrite DRCT cyls; use a guest to test that new 510RES IPL's and finds valid directory. Shutdown VM, use stand-alone DDR to copy new 510RES cyl 0 to old, and new 510RES DRCT cyls to old 510RES, re-IPL old 510RES -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 11:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume When it started to report the problem with the directory, I shutdown the system and IPLed with the original volume. I will IPL with the new volume and check to see if I can do a DIRECTXA with the user direct file. (We are using VM:Secure for directory management and as the ESM.) Thank you. Cecelia Dusha -Original Message- From: Romanowski, John (OFT) [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 11:10 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume The problem may have originated with the VTOC IBM shipped on cyl 0 of the VM5.1 System DDR of 510RES. It says 3340 cyls. CP doesn't care, it knows the pack is 3339 cyls. You CMS ACCESS-ed the device and CMS's Q DISK reported that the VTOC says the size is 3340 cyls. This 510RES VTOC bit me when our MVS folks ran a MVS tool to migrate our VM dasd to a DS8000 storage box; their dasd migration tool compared the VTOC size info against the actual pack size and quit if they didn't match. All of our VM5.1 systems had this VTOC discrepancy on 510RES and the tool wouldn't migrate them until I fixed cyl 0. Anyway, as Dave Kreuter pointed out, when you re-formatted cyl 0 you trashed the active-directory pointer. Hopefully you're in a position to run DIRECTXA with the source directory file and update that cyl 0 pointer. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: zVM 5.1 Res Volume I am experiencing a strange problem with my zVM 5.1 res volumes. The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be 3339 cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. When I attach this volume and access it, I get the following: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL 510RES 001 Z R/W 3340 3390OS I have tried the following: DDR to a new volume CPFMTXA FORMAT cylinder 0 CPFMTXA ALLOCATE system areas DRCT 1-20 PARM 21-38 PARM 39-128 PARM 129-188 SALIPL for the IPL data When this new volume (same name) is IPLed it says the directory is invalid... Any ideas as to what I should try next to get the res volume to see itself as a 3339 cylinder volume? Thank you. Cecelia Dush
Re: Question about ISPFVM on z/VM V5R2
In addition to 'Q SEGMENT', 'NUCXMAP' might help at least show what's loaded in the virtual machine. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Craig Dudley Sent: Friday, May 05, 2006 2:31 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Question about ISPFVM on z/VM V5R2 Dave, >the returned error code (41) gives a hint...the CMS storage where the >ISPF dcss needs to go is already being used by something else. My guest >is that your CMS user ids on your new 5.2 system are significantly >larger than they were on your old system. > >Try setting the virtual storage for the CMS guest down below the >location of the ISPF dcss and see if that doesn't at least allow ISPF >to start. > Yeah - it looks like there are some conflicts. Here is a partial of a q nss all map: FILE FILENAME FILETYPE MINSIZE BEGPAG ENDPAG TYPE CL #USERS PARMREGS VMGROUP 0021 NLSGER DCSS N/A02000 020FF SR A 0 N/A N/A 0020 NLSKANJI DCSS N/A02000 020FF SR A 0 N/A N/A 0035 NLSUCENG DCSS N/A02000 020FF SR A 0 N/A N/A 0034 NLSAMENG DCSS N/A02000 020FF SR A 00012 N/A N/A 0049 ISPDCSS DCSS N/A02000 020FF SR A 0 N/A N/A So now I need to figure out how to move the ISPDCSS to a new location. Or move the NLS DCSS. Any ideas as to which is easier? I don't know how to adapt the VM/XA or VM/SP HPO instructions to the newer environment. Are there any more modern instructions for changing the ISPDCSS BEGPAG? -- Thanks Craig >DJ > >Craig Dudley wrote: >> Hi, >> I am converting from a z/VM V3R1 system to a z/VM V5R2 system. I have >> ISPF VM V3R2 on my 3.1 system. I copied all the minidisks from the >> 3.1 system to the 5.2 system. I SPXTAPEd the ISPDCSS & SVM DCSS' from >> the 3.1 spool to the 5.2 spool. We XAUTOLOGed ISPVM on 5.2 and it >> came up without any >errors on >> the console log. This was verified by logging onto ISPVM and running >> the PROFILE manually. >> >> When my user tries to invoke ISPF for VM, I get: >> >> DMSSLG332E No user additions were loaded >> RETURN CODE FROM SEGMENT MACRO (LOADSYS) IS 41, SEE YOUR SYTEM PROGRAMMER >> ISPF DCSS SEGMENT NOT LOADED > >> 81 *-* 'ISPDCS ISPDCSS ISPVM 'arg >> string >>+++ RC(998) +++ >> >> With my 5.2 system I received a ISPF for VM V3R2 program directory >> but it seems to be written with VM/XA or VM/SP HPO in mind. >> >> So we are looking into the DMSSLG332E message. What we don't know is >> why the ISPDCS ISPDCSS ISPVM is failing. >> >> Please note that this is not ISPF/PDF, just ISPF. >> >> Any ideas would be appreciated. >> >> Thanks >> -- Craig Dudley Manager, Mainframe Technical Support Group Office of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1506Fax 603-271-1516 * This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. *
Re: Question about ISPFVM on z/VM V5R2
For what it's worth- We run zVM 5.1 and ISPDCSS is at 1F00-1FFF and ISRDCSS is at 2000-20FF. We don't use any language DCSS's. What size virtual stoarge does your id have (Q V STOR) and does 'Q SEGMENT' show anything loaded at the location ISPF wants? -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Craig Dudley Sent: Friday, May 05, 2006 2:31 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Question about ISPFVM on z/VM V5R2 Dave, >the returned error code (41) gives a hint...the CMS storage where the >ISPF dcss needs to go is already being used by something else. My guest >is that your CMS user ids on your new 5.2 system are significantly >larger than they were on your old system. > >Try setting the virtual storage for the CMS guest down below the >location of the ISPF dcss and see if that doesn't at least allow ISPF >to start. > Yeah - it looks like there are some conflicts. Here is a partial of a q nss all map: FILE FILENAME FILETYPE MINSIZE BEGPAG ENDPAG TYPE CL #USERS PARMREGS VMGROUP 0021 NLSGER DCSS N/A02000 020FF SR A 0 N/A N/A 0020 NLSKANJI DCSS N/A02000 020FF SR A 0 N/A N/A 0035 NLSUCENG DCSS N/A02000 020FF SR A 0 N/A N/A 0034 NLSAMENG DCSS N/A02000 020FF SR A 00012 N/A N/A 0049 ISPDCSS DCSS N/A02000 020FF SR A 0 N/A N/A So now I need to figure out how to move the ISPDCSS to a new location. Or move the NLS DCSS. Any ideas as to which is easier? I don't know how to adapt the VM/XA or VM/SP HPO instructions to the newer environment. Are there any more modern instructions for changing the ISPDCSS BEGPAG? -- Thanks Craig >DJ > >Craig Dudley wrote: >> Hi, >> I am converting from a z/VM V3R1 system to a z/VM V5R2 system. I have >> ISPF VM V3R2 on my 3.1 system. I copied all the minidisks from the >> 3.1 system to the 5.2 system. I SPXTAPEd the ISPDCSS & SVM DCSS' from >> the 3.1 spool to the 5.2 spool. We XAUTOLOGed ISPVM on 5.2 and it >> came up without any >errors on >> the console log. This was verified by logging onto ISPVM and running >> the PROFILE manually. >> >> When my user tries to invoke ISPF for VM, I get: >> >> DMSSLG332E No user additions were loaded >> RETURN CODE FROM SEGMENT MACRO (LOADSYS) IS 41, SEE YOUR SYTEM PROGRAMMER >> ISPF DCSS SEGMENT NOT LOADED > >> 81 *-* 'ISPDCS ISPDCSS ISPVM 'arg >> string >>+++ RC(998) +++ >> >> With my 5.2 system I received a ISPF for VM V3R2 program directory >> but it seems to be written with VM/XA or VM/SP HPO in mind. >> >> So we are looking into the DMSSLG332E message. What we don't know is >> why the ISPDCS ISPDCSS ISPVM is failing. >> >> Please note that this is not ISPF/PDF, just ISPF. >> >> Any ideas would be appreciated. >> >> Thanks >> -- Craig Dudley Manager, Mainframe Technical Support Group Office of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1506Fax 603-271-1516 * This communication, including attachments, is for the exclusive use of addressee and may contain proprietary, confidential and/or privileged information. If you are not the intended recipient, any use, copying, disclosure, dissemination or distribution is strictly prohibited. If you are not the intended recipient, please notify the sender immediately by return e-mail, delete this communication and destroy all copies. *
Re: Question about ISPFVM on z/VM V5R2
Dave, >the returned error code (41) gives a hint...the CMS storage where the >ISPF dcss needs to go is already being used by something else. My guest >is that your CMS user ids on your new 5.2 system are significantly >larger than they were on your old system. > >Try setting the virtual storage for the CMS guest down below the >location of the ISPF dcss and see if that doesn't at least allow ISPF to >start. > Yeah - it looks like there are some conflicts. Here is a partial of a q nss all map: FILE FILENAME FILETYPE MINSIZE BEGPAG ENDPAG TYPE CL #USERS PARMREGS VMGROUP 0021 NLSGER DCSS N/A02000 020FF SR A 0 N/A N/A 0020 NLSKANJI DCSS N/A02000 020FF SR A 0 N/A N/A 0035 NLSUCENG DCSS N/A02000 020FF SR A 0 N/A N/A 0034 NLSAMENG DCSS N/A02000 020FF SR A 00012 N/A N/A 0049 ISPDCSS DCSS N/A02000 020FF SR A 0 N/A N/A So now I need to figure out how to move the ISPDCSS to a new location. Or move the NLS DCSS. Any ideas as to which is easier? I don't know how to adapt the VM/XA or VM/SP HPO instructions to the newer environment. Are there any more modern instructions for changing the ISPDCSS BEGPAG? -- Thanks Craig >DJ > >Craig Dudley wrote: >> Hi, >> I am converting from a z/VM V3R1 system to a z/VM V5R2 system. I have ISPF >> VM V3R2 on my 3.1 system. I copied all the minidisks from the 3.1 system to >> the 5.2 system. I SPXTAPEd the ISPDCSS & SVM DCSS' from the 3.1 spool to >> the 5.2 spool. We XAUTOLOGed ISPVM on 5.2 and it came up without any >errors on >> the console log. This was verified by logging onto ISPVM and running the >> PROFILE manually. >> >> When my user tries to invoke ISPF for VM, I get: >> >> DMSSLG332E No user additions were loaded >> RETURN CODE FROM SEGMENT MACRO (LOADSYS) IS 41, SEE YOUR SYTEM PROGRAMMER >> ISPF DCSS SEGMENT NOT LOADED > >> 81 *-* 'ISPDCS ISPDCSS ISPVM 'arg >> string >>+++ RC(998) +++ >> >> With my 5.2 system I received a ISPF for VM V3R2 program directory but it >> seems to be written with VM/XA or VM/SP HPO in mind. >> >> So we are looking into the DMSSLG332E message. What we don't know is why >> the ISPDCS ISPDCSS ISPVM is failing. >> >> Please note that this is not ISPF/PDF, just ISPF. >> >> Any ideas would be appreciated. >> >> Thanks >> -- Craig Dudley Manager, Mainframe Technical Support Group Office of Information Technology State of New Hampshire 27 Hazen Drive Concord, NH 03301 603-271-1506Fax 603-271-1516
Re: Question about ISPFVM on z/VM V5R2
Craig, the returned error code (41) gives a hint...the CMS storage where the ISPF dcss needs to go is already being used by something else. My guest is that your CMS user ids on your new 5.2 system are significantly larger than they were on your old system. Try setting the virtual storage for the CMS guest down below the location of the ISPF dcss and see if that doesn't at least allow ISPF to start. DJ Craig Dudley wrote: Hi, I am converting from a z/VM V3R1 system to a z/VM V5R2 system. I have ISPF VM V3R2 on my 3.1 system. I copied all the minidisks from the 3.1 system to the 5.2 system. I SPXTAPEd the ISPDCSS & SVM DCSS' from the 3.1 spool to the 5.2 spool. We XAUTOLOGed ISPVM on 5.2 and it came up without any errors on the console log. This was verified by logging onto ISPVM and running the PROFILE manually. When my user tries to invoke ISPF for VM, I get: DMSSLG332E No user additions were loaded RETURN CODE FROM SEGMENT MACRO (LOADSYS) IS 41, SEE YOUR SYTEM PROGRAMMER ISPF DCSS SEGMENT NOT LOADED 81 *-* 'ISPDCS ISPDCSS ISPVM 'arg string +++ RC(998) +++ With my 5.2 system I received a ISPF for VM V3R2 program directory but it seems to be written with VM/XA or VM/SP HPO in mind. So we are looking into the DMSSLG332E message. What we don't know is why the ISPDCS ISPDCSS ISPVM is failing. Please note that this is not ISPF/PDF, just ISPF. Any ideas would be appreciated. Thanks
Re: ZVM 5.2 and ISPVM
Jim, just do the following: 1) create a new ISPFVM user id on your new z/VM system that matches the ISPFVM user id on your old 3.1 system 2) copy the contents of the old ISPFVM minidisks over to the new 5.2 system 3) either recreate the needed ISPF dcss-es (I think they're named ISPDCSS and ISRDCSS) or copy them from the 3.1 spool space to the 5.2 spool space. That should do it DJ Hughes, Jim - OIT wrote: I'd like to move ISPVM from our ZVM 3.1 system to our new ZVM 5.2 system. Is there a simple way to relocate the product? If so, what are the steps?? Thanks in advance. ___ Jim Hughes 603-271-5586 "Impossible is just an opinion."
Re: Question about ISPFVM on z/VM V5R2
Could it be 41 The storage required to load the saved segment is already in use. Either the required virtual machine storage has already been allocated by CMS or storage outside the virtual machine has been reserved for another saved segment. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Craig Dudley Sent: Friday, May 05, 2006 1:42 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Question about ISPFVM on z/VM V5R2 Hi, I am converting from a z/VM V3R1 system to a z/VM V5R2 system. I have ISPF VM V3R2 on my 3.1 system. I copied all the minidisks from the 3.1 system to the 5.2 system. I SPXTAPEd the ISPDCSS & SVM DCSS' from the 3.1 spool to the 5.2 spool. We XAUTOLOGed ISPVM on 5.2 and it came up without any errors on the console log. This was verified by logging onto ISPVM and running the PROFILE manually. When my user tries to invoke ISPF for VM, I get: DMSSLG332E No user additions were loaded RETURN CODE FROM SEGMENT MACRO (LOADSYS) IS 41, SEE YOUR SYTEM PROGRAMMER ISPF DCSS SEGMENT NOT LOADED 81 *-* 'ISPDCS ISPDCSS ISPVM 'arg string +++ RC(998) +++ With my 5.2 system I received a ISPF for VM V3R2 program directory but it seems to be written with VM/XA or VM/SP HPO in mind. So we are looking into the DMSSLG332E message. What we don't know is why the ISPDCS ISPDCSS ISPVM is failing. Please note that this is not ISPF/PDF, just ISPF. Any ideas would be appreciated. Thanks -- Craig Dudley
ZVM 5.2 and ISPVM
I'd like to move ISPVM from our ZVM 3.1 system to our new ZVM 5.2 system. Is there a simple way to relocate the product? If so, what are the steps?? Thanks in advance. ___ Jim Hughes 603-271-5586 "Impossible is just an opinion."
Question about ISPFVM on z/VM V5R2
Hi, I am converting from a z/VM V3R1 system to a z/VM V5R2 system. I have ISPF VM V3R2 on my 3.1 system. I copied all the minidisks from the 3.1 system to the 5.2 system. I SPXTAPEd the ISPDCSS & SVM DCSS' from the 3.1 spool to the 5.2 spool. We XAUTOLOGed ISPVM on 5.2 and it came up without any errors on the console log. This was verified by logging onto ISPVM and running the PROFILE manually. When my user tries to invoke ISPF for VM, I get: DMSSLG332E No user additions were loaded RETURN CODE FROM SEGMENT MACRO (LOADSYS) IS 41, SEE YOUR SYTEM PROGRAMMER ISPF DCSS SEGMENT NOT LOADED 81 *-* 'ISPDCS ISPDCSS ISPVM 'arg string +++ RC(998) +++ With my 5.2 system I received a ISPF for VM V3R2 program directory but it seems to be written with VM/XA or VM/SP HPO in mind. So we are looking into the DMSSLG332E message. What we don't know is why the ISPDCS ISPDCSS ISPVM is failing. Please note that this is not ISPF/PDF, just ISPF. Any ideas would be appreciated. Thanks -- Craig Dudley
Re: zVM 5.1 Res Volume
You said you DDR-ed the old 510RES to the new 510RES and reworked cyl 0 of the new 510RES; and you're running now using the old 510RES. So you can fix the new 510RES's cyl 0 from the VM system that's still running off the old 510RES, no need to IPL the new 510RES first with the NODIRECT option and try to fix it (easier to do it that way on a guest). First, To avoid issues of old 510RES's contents having diverged from new 510RES's, repeat your steps that DDR-ed the old to new 510RES, , CPFMTXA, etc. Then on MAINT, Get your latest CP directory in source file format as file USER DIRECT A (on userid VMXSYSAD do VMXBKP01 NOTAPE to create file USER DIRECT) The DIRECTORY statement in USER DIRECT says DIRECTORY ... ATTACH the new 510RES to MAINT at virtual addr Response from CP Q V should then say: DASD ON DASD R/W 510RES ... Then fix new 510RES's active-directory pointer in cyl 0 DIRECTXA USER DIRECT A (TEST DIRECTXA USER DIRECT A Will update the new 510RES object directory (DRCT area) and fix its cyl 0 active-directory pointer. You could also do this more safely from a class G userid to which you attach as and give the USER DIRECT A file. Then shutdown VM and re-ipl using the new fixed 510RES. VMSECURE's 191 file DIRECT STATEMNT, still has the old 510RES device address, , in it. You'll want to fix that file to change to . Alternative: don't ddr entire old 510RES to new, just run the DIRECTXA steps to fix new 510RES cyl 0 and rewrite DRCT cyls; use a guest to test that new 510RES IPL's and finds valid directory. Shutdown VM, use stand-alone DDR to copy new 510RES cyl 0 to old, and new 510RES DRCT cyls to old 510RES, re-IPL old 510RES -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 11:45 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume When it started to report the problem with the directory, I shutdown the system and IPLed with the original volume. I will IPL with the new volume and check to see if I can do a DIRECTXA with the user direct file. (We are using VM:Secure for directory management and as the ESM.) Thank you. Cecelia Dusha -Original Message- From: Romanowski, John (OFT) [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 11:10 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume The problem may have originated with the VTOC IBM shipped on cyl 0 of the VM5.1 System DDR of 510RES. It says 3340 cyls. CP doesn't care, it knows the pack is 3339 cyls. You CMS ACCESS-ed the device and CMS's Q DISK reported that the VTOC says the size is 3340 cyls. This 510RES VTOC bit me when our MVS folks ran a MVS tool to migrate our VM dasd to a DS8000 storage box; their dasd migration tool compared the VTOC size info against the actual pack size and quit if they didn't match. All of our VM5.1 systems had this VTOC discrepancy on 510RES and the tool wouldn't migrate them until I fixed cyl 0. Anyway, as Dave Kreuter pointed out, when you re-formatted cyl 0 you trashed the active-directory pointer. Hopefully you're in a position to run DIRECTXA with the source directory file and update that cyl 0 pointer. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: zVM 5.1 Res Volume I am experiencing a strange problem with my zVM 5.1 res volumes. The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be 3339 cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. When I attach this volume and access it, I get the following: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL 510RES 001 Z R/W 3340 3390OS I have tried the following: DDR to a new volume CPFMTXA FORMAT cylinder 0 CPFMTXA ALLOCATE system areas DRCT 1-20 PARM 21-38 PARM 39-128 PARM 129-188 SALIPL for the IPL data When this new volume (same name) is IPLed it says the directory is invalid... Any ideas as to what I should try next to get the res volume to see itself as a 3339 cylinder volume? Thank you. Cecelia Dusha
Re: zVM 5.1 Res Volume
Once you get the directory rebuilt you'll want to start VMSECURE with the SOURCE option. This will insure your online directory and VMSECURE data base are in synch. Brian Nielsen On Fri, 5 May 2006 15:44:31 -, Dusha, Cecelia Ms. WHS/ITMD <[EMAIL PROTECTED]> wrote: >When it started to report the problem with the directory, I shutdown the >system and IPLed with the original volume. I will IPL with the new volu me >and check to see if I can do a DIRECTXA with the user direct file. (We are >using VM:Secure for directory management and as the ESM.) > >Thank you. > >Cecelia Dusha >-Original Message- >From: Romanowski, John (OFT) [mailto:[EMAIL PROTECTED] >Sent: Friday, May 05, 2006 11:10 AM >To: IBMVM@LISTSERV.UARK.EDU >Subject: Re: zVM 5.1 Res Volume > >The problem may have originated with the VTOC IBM shipped on cyl 0 of >the VM5.1 System DDR of 510RES. It says 3340 cyls. CP doesn't care, it >knows the pack is 3339 cyls. > > You CMS ACCESS-ed the device and CMS's Q DISK reported that the VTOC >says the size is 3340 cyls. > >This 510RES VTOC bit me when our MVS folks ran a MVS tool to migrate our >VM dasd to a DS8000 storage box; their dasd migration tool compared the >VTOC size info against the actual pack size and quit if they didn't >match. > All of our VM5.1 systems had this VTOC discrepancy on 510RES and the >tool wouldn't migrate them until I fixed cyl 0. > >Anyway, as Dave Kreuter pointed out, when you re-formatted cyl 0 you >trashed the active-directory pointer. Hopefully you're in a position to >run DIRECTXA with the source directory file and update that cyl 0 >pointer. > > > > >This e-mail, including any attachments, may be confidential, privileged or >otherwise legally protected. It is intended only for the addressee. If y ou >received this e-mail in error or from someone who was not authorized to send >it to you, do not disseminate, copy or otherwise use this e-mail or its >attachments. Please notify the sender immediately by reply e-mail and >delete the e-mail from your system. > > >-Original Message- > >From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >Behalf Of Dusha, Cecelia Ms. WHS/ITMD >Sent: Friday, May 05, 2006 10:19 AM >To: IBMVM@LISTSERV.UARK.EDU >Subject: zVM 5.1 Res Volume > >I am experiencing a strange problem with my zVM 5.1 res volumes. > >The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be >3339 >cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. > >When I attach this volume and access it, I get the following: >LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT >BLK >TOTAL >510RES 001 Z R/W 3340 3390OS > > >I have tried the following: >DDR to a new volume >CPFMTXA FORMAT cylinder 0 >CPFMTXA ALLOCATE system areas > DRCT 1-20 > PARM 21-38 > PARM 39-128 > PARM 129-188 >SALIPL for the IPL data > >When this new volume (same name) is IPLed it says the directory is >invalid... > >Any ideas as to what I should try next to get the res volume to see >itself >as a 3339 cylinder volume? > >Thank you. > >Cecelia Dusha
Re: zVM 5.1 Res Volume
When it started to report the problem with the directory, I shutdown the system and IPLed with the original volume. I will IPL with the new volume and check to see if I can do a DIRECTXA with the user direct file. (We are using VM:Secure for directory management and as the ESM.) Thank you. Cecelia Dusha -Original Message- From: Romanowski, John (OFT) [mailto:[EMAIL PROTECTED] Sent: Friday, May 05, 2006 11:10 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: zVM 5.1 Res Volume The problem may have originated with the VTOC IBM shipped on cyl 0 of the VM5.1 System DDR of 510RES. It says 3340 cyls. CP doesn't care, it knows the pack is 3339 cyls. You CMS ACCESS-ed the device and CMS's Q DISK reported that the VTOC says the size is 3340 cyls. This 510RES VTOC bit me when our MVS folks ran a MVS tool to migrate our VM dasd to a DS8000 storage box; their dasd migration tool compared the VTOC size info against the actual pack size and quit if they didn't match. All of our VM5.1 systems had this VTOC discrepancy on 510RES and the tool wouldn't migrate them until I fixed cyl 0. Anyway, as Dave Kreuter pointed out, when you re-formatted cyl 0 you trashed the active-directory pointer. Hopefully you're in a position to run DIRECTXA with the source directory file and update that cyl 0 pointer. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: zVM 5.1 Res Volume I am experiencing a strange problem with my zVM 5.1 res volumes. The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be 3339 cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. When I attach this volume and access it, I get the following: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL 510RES 001 Z R/W 3340 3390OS I have tried the following: DDR to a new volume CPFMTXA FORMAT cylinder 0 CPFMTXA ALLOCATE system areas DRCT 1-20 PARM 21-38 PARM 39-128 PARM 129-188 SALIPL for the IPL data When this new volume (same name) is IPLed it says the directory is invalid... Any ideas as to what I should try next to get the res volume to see itself as a 3339 cylinder volume? Thank you. Cecelia Dusha
Re: zVM 5.1 Res Volume
Formatting Cyl 0 also wiped out the Stand Alone Loader. You need to reload it using the SALIPL command. Jim At 11:09 AM 5/5/2006, you wrote: The problem may have originated with the VTOC IBM shipped on cyl 0 of the VM5.1 System DDR of 510RES. It says 3340 cyls. CP doesn't care, it knows the pack is 3339 cyls. You CMS ACCESS-ed the device and CMS's Q DISK reported that the VTOC says the size is 3340 cyls. This 510RES VTOC bit me when our MVS folks ran a MVS tool to migrate our VM dasd to a DS8000 storage box; their dasd migration tool compared the VTOC size info against the actual pack size and quit if they didn't match. All of our VM5.1 systems had this VTOC discrepancy on 510RES and the tool wouldn't migrate them until I fixed cyl 0. Anyway, as Dave Kreuter pointed out, when you re-formatted cyl 0 you trashed the active-directory pointer. Hopefully you're in a position to run DIRECTXA with the source directory file and update that cyl 0 pointer.=20 This e-mail, including any attachments, may be confidential, privileged = or otherwise legally protected. It is intended only for the addressee. = If you received this e-mail in error or from someone who was not = authorized to send it to you, do not disseminate, copy or otherwise use = this e-mail or its attachments. Please notify the sender immediately by = reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: zVM 5.1 Res Volume I am experiencing a strange problem with my zVM 5.1 res volumes. The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be 3339 cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. When I attach this volume and access it, I get the following: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL 510RES 001 Z R/W 3340 3390OS I have tried the following: DDR to a new volume CPFMTXA FORMAT cylinder 0 CPFMTXA ALLOCATE system areas DRCT 1-20 PARM 21-38 PARM 39-128 PARM 129-188 SALIPL for the IPL data When this new volume (same name) is IPLed it says the directory is invalid... Any ideas as to what I should try next to get the res volume to see itself as a 3339 cylinder volume? Thank you. =20 Cecelia Dusha Jim Bohnsack Cornell Univ. (607) 255-1760
Re: zVM 5.1 Res Volume
The problem may have originated with the VTOC IBM shipped on cyl 0 of the VM5.1 System DDR of 510RES. It says 3340 cyls. CP doesn't care, it knows the pack is 3339 cyls. You CMS ACCESS-ed the device and CMS's Q DISK reported that the VTOC says the size is 3340 cyls. This 510RES VTOC bit me when our MVS folks ran a MVS tool to migrate our VM dasd to a DS8000 storage box; their dasd migration tool compared the VTOC size info against the actual pack size and quit if they didn't match. All of our VM5.1 systems had this VTOC discrepancy on 510RES and the tool wouldn't migrate them until I fixed cyl 0. Anyway, as Dave Kreuter pointed out, when you re-formatted cyl 0 you trashed the active-directory pointer. Hopefully you're in a position to run DIRECTXA with the source directory file and update that cyl 0 pointer. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Dusha, Cecelia Ms. WHS/ITMD Sent: Friday, May 05, 2006 10:19 AM To: IBMVM@LISTSERV.UARK.EDU Subject: zVM 5.1 Res Volume I am experiencing a strange problem with my zVM 5.1 res volumes. The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be 3339 cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. When I attach this volume and access it, I get the following: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL 510RES 001 Z R/W 3340 3390OS I have tried the following: DDR to a new volume CPFMTXA FORMAT cylinder 0 CPFMTXA ALLOCATE system areas DRCT 1-20 PARM 21-38 PARM 39-128 PARM 129-188 SALIPL for the IPL data When this new volume (same name) is IPLed it says the directory is invalid... Any ideas as to what I should try next to get the res volume to see itself as a 3339 cylinder volume? Thank you. Cecelia Dusha
Re: zVM 5.1 Res Volume
Hi: When you formatted cyl 0 you blew away the byte structure that indicates which half of the directory cylinders are in use. So CP doesn't have a usable directory. So that's one problem. Dvid Dusha, Cecelia Ms. WHS/ITMD wrote: CPFMTXA FORMAT cylinder 0
zVM 5.1 Res Volume
I am experiencing a strange problem with my zVM 5.1 res volumes. The zVM 5.1 res volume is on a 3390 mod 3 pack. This volume should be 3339 cylinders. It is on DASD carved from a DS6800 as 3339 cylinders. When I attach this volume and access it, I get the following: LABEL VDEV M STAT CYL TYPE BLKSZ FILES BLKS USED-(%) BLKS LEFT BLK TOTAL 510RES 001 Z R/W 3340 3390OS I have tried the following: DDR to a new volume CPFMTXA FORMAT cylinder 0 CPFMTXA ALLOCATE system areas DRCT 1-20 PARM 21-38 PARM 39-128 PARM 129-188 SALIPL for the IPL data When this new volume (same name) is IPLed it says the directory is invalid... Any ideas as to what I should try next to get the res volume to see itself as a 3339 cylinder volume? Thank you. Cecelia Dusha
Re: Tape, DFSMS/VM and RMS
Hi Steve, If you like, you can manually verify RMS and the 3494 are working together before trying to get VM:Tape to use RMS and the 3494; that might simplify troubleshooting your implementation. Use the DFSMS/VM RMS User’s Guide, Chapter 6 “DFSMSRM Commands” to manually query and operate the 3494. From userid DFSMS with mdisk 1B5 accessed, enter some DFSMSRM commands like DFSMSRM QUERY LIBRARY OPSTATE to see if RMS can communicate with the 3494 and get its status. DFSMSRM QUERY LIBRARY DEVICE rdev to query status of a 3494 tape drive address DFSMSRM QUERY LIBRARY INVENTORY INSERT to see if any volids aren’t assigned a target category DFSMSRM QUERY LIBRARY INVENTORY SCRATCHx There are only about 8 RMS commands; you can manually mount 3494 tapes, etc. before trying to get the VMTAPE RMS interface working. If you have VM:Operator, it’s helpful to have userid OPERATOR as the secuser of RMSMASTR so RMSMASTR’s messages are logged for review. This e-mail, including any attachments, may be confidential, privileged or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Steve Gentry Sent: Friday, May 05, 2006 9:17 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: Tape, DFSMS/VM and RMS I've read this part of the CA manual and it seemed pretty straight forward. I guess the part I'm curious about is the VM/IBM side of things. I came across one doc. and it dedicated a Chap. to VM:Tape. It talks about setting up a programmable operator to intercept the mount requests and then issue the proper 3494 mount commands. Is this still needed? Does CA supply the pieces to plug into the programmable operator? I've contacted CA support and am waiting for a reply. They have been very helpful. Steve G. "Imler, Steven J" <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System 05/05/2006 07:12 AM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: Tape, DFSMS/VM and RMS After following Les' recommendations for installing and customizing the RMS component of DFSMS/VM, review and follow the instructions in the VM:Tape System Administrator's Guide; Appendix D, IBM Tape Library Data Server. Those steps will guide you to: --> Update your VMTAPE CONFIG file --> Update the DFSMS/VM DGTAUTH DATA file --> Ensure that the VM:Tape virtual machine is LINKED and ACCESSED to the DFSMS "run disk" (usually the DFSMS 1B5 minidisk) --> Issue a VMTAPE START RMS command --> Issue a VMTAPE SET LOCATION command if needed If you have more questions, please call CA's VM Customer Support ... JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Les Geer (607-429-3580) Sent: Thursday, May 04, 2006 10:52 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VM:Tape, DFSMS/VM and RMS >I'm at a point where I'm trying to figure out what specific pieces are >needed to get the items listed in the subject line above >and a 3494 to work together. This is the first time I've worked with a >3494, DFSMS/VM and RMS. I've read some of the manuals, >both IBM and CA, and am a little confused as to what needs to be config'd >on each of the products listed.. > You will want to install the RMS component of DFSMS/VM (RMSONLY) then follow setup information in chapter 2 of the RMS User's Guide. Best Regards, Les Geer IBM z/VM and Linux Development
Re: DS6000
Just a check, what release of ICKDSF? Should be 1.17. Ed Martin Aultman Health Foundation 330-588-4723 [EMAIL PROTECTED] ext. 40441 >> -Original Message- >> From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On >> Behalf Of [EMAIL PROTECTED] >> Sent: Thursday, May 04, 2006 4:35 PM >> To: IBMVM@LISTSERV.UARK.EDU >> Subject: DS6000 >> >> Running VM 5.1 >> >> Anyone having trouble with plain ICKDSF in VM could writing VTOC record >> above the 3338 cylinder for a 3390-9?
Re: Tape, DFSMS/VM and RMS
Well, I have not read that, I don't even have VM:Tape at all. But I will say that setting up PROP to respond to tape requests from VM:Backup was a cinch. OPERATOR is defined as a tape op, and gets the mount request. It immediately runs a DFSMSRM MOUNT command, and the backup runs. Shimon On 5 May 2006 at 8:17, Steve Gentry wrote: > I've read this part of the CA manual and it seemed pretty straight > forward. I guess the part I'm curious about is the VM/IBM side of things. > I came across one doc. and it dedicated a Chap. to VM:Tape. It talks > about setting up a programmable operator to intercept the > mount requests and then issue the proper 3494 mount commands. Is this > still needed? Does CA supply the pieces to plug into > the programmable operator? I've contacted CA support and am waiting for a > reply. They have been very helpful. Steve G. > > > > > > "Imler, Steven J" <[EMAIL PROTECTED]> > Sent by: The IBM z/VM Operating System > 05/05/2006 07:12 AM > Please respond to The IBM z/VM Operating System > > > To: IBMVM@LISTSERV.UARK.EDU > cc: > Subject:Re: Tape, DFSMS/VM and RMS > > > After following Les' recommendations for installing and customizing the > RMS component of DFSMS/VM, review and follow the instructions in the > VM:Tape System Administrator's Guide; Appendix D, IBM Tape Library Data > Server. > > Those steps will guide you to: > > --> Update your VMTAPE CONFIG file > --> Update the DFSMS/VM DGTAUTH DATA file > --> Ensure that the VM:Tape virtual machine is LINKED and ACCESSED > to the DFSMS "run disk" (usually the DFSMS 1B5 minidisk) > --> Issue a VMTAPE START RMS command > --> Issue a VMTAPE SET LOCATION command if needed > > If you have more questions, please call CA's VM Customer Support ... > > JR (Steven) Imler > CA > Senior Software Engineer > Tel: +1 703 708 3479 > Fax: +1 703 708 3267 > [EMAIL PROTECTED] > >
Re: Tape, DFSMS/VM and RMS
Steve, No, you don't need to set up any PROP or VM:Operator action routines to interface VM:Tape with IBM 3494. VM:Tape communicates directly with the RMSMASTR virtual machine to accomplish tape mounts ... no automation is required. Hmm ... I wasn't aware of the documentation you've referenced, but at this point it is completely obsolete and you can ignore it. 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 Steve GentrySent: Friday, May 05, 2006 09:17 AMTo: IBMVM@LISTSERV.UARK.EDUSubject: Re: Tape, DFSMS/VM and RMS I've read this part of the CA manual and it seemed pretty straight forward. I guess the part I'm curious about is the VM/IBM side of things. I came across one doc. and it dedicated a Chap. to VM:Tape. It talks about setting up a programmable operator to intercept the mount requests and then issue the proper 3494 mount commands. Is this still needed? Does CA supply the pieces to plug into the programmable operator? I've contacted CA support and am waiting for a reply. They have been very helpful. Steve G. "Imler, Steven J" <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System 05/05/2006 07:12 AM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: Tape, DFSMS/VM and RMSAfter following Les' recommendations for installing and customizing theRMS component of DFSMS/VM, review and follow the instructions in theVM:Tape System Administrator's Guide; Appendix D, IBM Tape Library DataServer.Those steps will guide you to:--> Update your VMTAPE CONFIG file --> Update the DFSMS/VM DGTAUTH DATA file--> Ensure that the VM:Tape virtual machine is LINKED and ACCESSED to the DFSMS "run disk" (usually the DFSMS 1B5 minidisk)--> Issue a VMTAPE START RMS command--> Issue a VMTAPE SET LOCATION command if neededIf you have more questions, please call CA's VM Customer Support ...JR (Steven) ImlerCASenior Software EngineerTel: +1 703 708 3479Fax: +1 703 708 3267[EMAIL PROTECTED]-Original Message-From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] OnBehalf Of Les Geer (607-429-3580)Sent: Thursday, May 04, 2006 10:52 PMTo: IBMVM@LISTSERV.UARK.EDUSubject: VM:Tape, DFSMS/VM and RMS>I'm at a point where I'm trying to figure out what specific pieces are>needed to get the items listed in the subject line above>and a 3494 to work together. This is the first time I've worked with a>3494, DFSMS/VM and RMS. I've read some of the manuals,>both IBM and CA, and am a little confused as to what needs to beconfig'd>on each of the products listed..>You will want to install the RMS component of DFSMS/VM (RMSONLY)then follow setup information in chapter 2 of the RMS User's Guide.Best Regards,Les GeerIBM z/VM and Linux Development
Re: Tape, DFSMS/VM and RMS
I've read this part of the CA manual and it seemed pretty straight forward. I guess the part I'm curious about is the VM/IBM side of things. I came across one doc. and it dedicated a Chap. to VM:Tape. It talks about setting up a programmable operator to intercept the mount requests and then issue the proper 3494 mount commands. Is this still needed? Does CA supply the pieces to plug into the programmable operator? I've contacted CA support and am waiting for a reply. They have been very helpful. Steve G. "Imler, Steven J" <[EMAIL PROTECTED]> Sent by: The IBM z/VM Operating System 05/05/2006 07:12 AM Please respond to The IBM z/VM Operating System To: IBMVM@LISTSERV.UARK.EDU cc: Subject: Re: Tape, DFSMS/VM and RMS After following Les' recommendations for installing and customizing the RMS component of DFSMS/VM, review and follow the instructions in the VM:Tape System Administrator's Guide; Appendix D, IBM Tape Library Data Server. Those steps will guide you to: --> Update your VMTAPE CONFIG file --> Update the DFSMS/VM DGTAUTH DATA file --> Ensure that the VM:Tape virtual machine is LINKED and ACCESSED to the DFSMS "run disk" (usually the DFSMS 1B5 minidisk) --> Issue a VMTAPE START RMS command --> Issue a VMTAPE SET LOCATION command if needed If you have more questions, please call CA's VM Customer Support ... JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Les Geer (607-429-3580) Sent: Thursday, May 04, 2006 10:52 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VM:Tape, DFSMS/VM and RMS >I'm at a point where I'm trying to figure out what specific pieces are >needed to get the items listed in the subject line above >and a 3494 to work together. This is the first time I've worked with a >3494, DFSMS/VM and RMS. I've read some of the manuals, >both IBM and CA, and am a little confused as to what needs to be config'd >on each of the products listed.. > You will want to install the RMS component of DFSMS/VM (RMSONLY) then follow setup information in chapter 2 of the RMS User's Guide. Best Regards, Les Geer IBM z/VM and Linux Development
Re: Tape, DFSMS/VM and RMS
After following Les' recommendations for installing and customizing the RMS component of DFSMS/VM, review and follow the instructions in the VM:Tape System Administrator's Guide; Appendix D, IBM Tape Library Data Server. Those steps will guide you to: --> Update your VMTAPE CONFIG file --> Update the DFSMS/VM DGTAUTH DATA file --> Ensure that the VM:Tape virtual machine is LINKED and ACCESSED to the DFSMS "run disk" (usually the DFSMS 1B5 minidisk) --> Issue a VMTAPE START RMS command --> Issue a VMTAPE SET LOCATION command if needed If you have more questions, please call CA's VM Customer Support ... JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Les Geer (607-429-3580) Sent: Thursday, May 04, 2006 10:52 PM To: IBMVM@LISTSERV.UARK.EDU Subject: VM:Tape, DFSMS/VM and RMS >I'm at a point where I'm trying to figure out what specific pieces are >needed to get the items listed in the subject line above >and a 3494 to work together. This is the first time I've worked with a >3494, DFSMS/VM and RMS. I've read some of the manuals, >both IBM and CA, and am a little confused as to what needs to be config'd >on each of the products listed.. > You will want to install the RMS component of DFSMS/VM (RMSONLY) then follow setup information in chapter 2 of the RMS User's Guide. Best Regards, Les Geer IBM z/VM and Linux Development
Re: Question about diskmap
--- Rob van der Heij <[EMAIL PROTECTED]> wrote: > On 5/4/06, Larry Macioce > <[EMAIL PROTECTED]> wrote: > > > MDISK 5F0 3380 501 1 $$ MR > > MDISK 5FF 3380 502 1 $$ MR > > Does this look familiar ?? > > These are just place holders for 2 mini disks for > DATAMOVE. Used to be > that DFSMS did that, but probably DirMaint can too > these days. I think DATAMOVE has "always" (well as long as it has existed) been able to that. I think its been around a tad longer than DFSMS. > When > DirMaint needs DATAMOVE to copy a disk it uses > DIAG84 to dynamically > replace the actual mini disk definition. So it > virtually moves the > extent from the user to the datamove machine. It > avoids the overhead > of a source update and full directxa. > > Since you are doing diskmap, I guess you don't run > DirMaint and got > the DATAMOVE entry for free with the pre-installed > (but not active) > DirMaint stuff. In that case you can ignore the > entries. And if you > don't plan to license DirMaint you might comment out > these entries to > get them out of the report. > > Rob > > -- > Rob van der Heij > Velocity Software, Inc > http://velocitysoftware.com/ > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: DS6000
I don't have the details handy ... but I seem to recall this was an ICKDSF bug. JR (Steven) Imler CA Senior Software Engineer Tel: +1 703 708 3479 Fax: +1 703 708 3267 [EMAIL PROTECTED] -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Thursday, May 04, 2006 05:36 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: DS6000 well, it would be a full pack mini disk. They are just trying to init a 3390-9 to put a vtoc on it. All they get is the 3338 cyls. They went to VM 5.1 to be able to get the DS6000.
Arjen Neij/AMS/KAS is out of the office.
I will be out of the office starting 05-05-2006 and will not return until 15-05-2006. I will respond to your message when I return. ** Disclaimer The information contained in this message is intended only for the person or entity to whom it is addressed and may contain confidential and/or privacy sensitive information. If you are not the addressee of this message, you may not use, distribute or disclose this information in any way. If you have received this message mistakenly, please notify us immediately and destroy this message forthwith. KAS BANK N.V. does not guarantee that the information contained in this message will be correctly or entirely received by the recipient.
Re: Question about diskmap
On 5/4/06, Larry Macioce <[EMAIL PROTECTED]> wrote: MDISK 5F0 3380 501 1 $$ MR MDISK 5FF 3380 502 1 $$ MR Does this look familiar ?? These are just place holders for 2 mini disks for DATAMOVE. Used to be that DFSMS did that, but probably DirMaint can too these days. When DirMaint needs DATAMOVE to copy a disk it uses DIAG84 to dynamically replace the actual mini disk definition. So it virtually moves the extent from the user to the datamove machine. It avoids the overhead of a source update and full directxa. Since you are doing diskmap, I guess you don't run DirMaint and got the DATAMOVE entry for free with the pre-installed (but not active) DirMaint stuff. In that case you can ignore the entries. And if you don't plan to license DirMaint you might comment out these entries to get them out of the report. Rob -- Rob van der Heij Velocity Software, Inc http://velocitysoftware.com/
