Re: RSCS LPR Printer Name w/spaces
Fran Hensler wrote: I enclosed the printer name in single quotes but I get a NAK when I try to print to it. PRINTER='eX- Printer on https://xxx.xx-.us/printers/default' Does anyone know how I could either rename this printer to remove spaces or how to make RSCS print to printer name with embedded spaces. On Tue, 12 Dec 2006 12:14:37 -0500 David Boyes said: Have the machine that has access to the printer share it as a name that does not have spaces in it. The Windows LPD will honor shared names as well as the original name. David - Your solution worked great when testing on a local network printer but when I tried to share the IPP printer I got this message Sharing is not supported for this type of printer I tried creating a short cut but that doesn't work either. So I'm going to try and get the vendor to change the spaces in the printer name to underscores. I might also open a PMR and ask IBM to support printer names with embedded spaces in the name. /Fran Hensler at Slippery Rock University of Pennsylvania USA for 43 years [EMAIL PROTECTED] +1.724.738.2153 Yes, Virginia, there is a Slippery Rock
Re: RSCS LPR Printer Name w/spaces
On Thursday, 12/14/2006 at 08:36 EST, Fran Hensler [EMAIL PROTECTED] wrote: Your solution worked great when testing on a local network printer but when I tried to share the IPP printer I got this message Sharing is not supported for this type of printer I tried creating a short cut but that doesn't work either. So I'm going to try and get the vendor to change the spaces in the printer name to underscores. I might also open a PMR and ask IBM to support printer names with embedded spaces in the name. While you get it straightened out, you can use TCPSNIFF (VM download library?) to act as an LPR proxy, changing RSCS-specifed underscores to blanks on the way to the printer. However, using blanks in LPR queue names violates RFC 1179 (LPR), since blanks are significant to the protocol for 'query' and 'remove' functions. Alan Altmark z/VM Development IBM Endicott
Re: Sysprof Exec in z/vm 4.4
Thanks to everyone for their help on Sysprof. I used Mike's suggestion below and it worked like a charm. The new z/vm 4.4 system dust is starting to settle. Anyone game for another question... Yesterday on our new 4.4 system, I was deleting some old users on random packs using Dirmaint while logged onto Maint. Our person who runs Vmbackup was logged on her Vmrmaint account running backups. All the Vmbackup and Vmrmaint mdisks are on the old 230RES pack that we now have attached to the 4.4 system as CP System. The Vmbackup person called me to say that all the mdisks for vmbackup and vmrmaint were empty (she never logged off) and upon checking myself, somehow 230RES was relabeled to SCRTCH. Wow, was that a shocker for me! I immediately restored a backup that I had but am now searching for the reason this happened. Dirmaint? Thanks again for any help. Mary Zervos Binghamton University Mike Walter wrote: As noted by another listserv member, it's probably the need to resave INSTSEG. It can get really tough remembering all the things one needs to do to build, install, test, and move local mods into production. I started using the AUX files as a repository of such local information because that where I trip over it when needing to modify something. SYSPROF mods are only one of many, including vendor products. We use AUX files named AUXRS (for ouR Stuff) so they are easy to find, not being the name of any IBM or ISV AUX files. You may not want to bother with that technique. Here's an example... modify it to meet your needs if you wish: SYSPROF AUXRSD1 F 80 Trunc=80 Size=15 Line=0 Col=1 Alt=0 |...+1+2+3+4+5+6+7+ * * * Top of File * * * RS0040DS 501 RS040DS Update SYSPROF with local enhancements. * To create, be sure to copy the proper SYSPROF $EXEC to the A-disk * (EXECUPDT overwrites the SYSPROF EXEC on the same disk as the $EXEC)! * To update SYSPROF EXEC, you should: * COPY SYSPROF $EXEC fm = = A (OLDDATE REPLACE UNPACK -- See UNPACK! * XEDITSYSPROF $EXEC * (CTL DMSVM SID RS0040DS, then * EXECUPDT SYSPROF EXEC * (CTL DMSVM HISTory SID * Test the SYSPROF EXEC (esp. for syntax errors!) * COPY SYSPROF EXEC A = EXC040DS E (OLDDate REPLace * so VMFBLD won't complain later on. * COPY SYSPROF EXEC A = EXEC E (OLDDate REPLace ERASE * so we don't get mixed up. * then re-save the INSTSEG NSS, e.g. * CP IPL 190 CLEAR PARM NOSPROF INSTSEG NO MTSEG NO * VMFBLD PPF SEGBLD ESASEGS SEGBLIST INSTSEG ( ALL * * * End of File * * * Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. *Mary Zervos [EMAIL PROTECTED]* Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 12/13/2006 10:28 AM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Sysprof Exec in z/vm 4.4 Well, we finally migrated to z/vm 4.4 two days ago from vm/esa 2.3. Most of our little fires are out. But here's a new problem for us..we tailor our Sysprof Exec to run an account exec before a users's profile exec. For some reason, Sysprof exec is not being run when we Ipl Cms or Ipl 190. Did something change with Sysprof Exec since vm/esa 2.3? Is it still automatically run as part of the CMS initialization procedure when a user logs on or reIpls CMS? Thanks for any help. We've even traced the original z/vm 4.4 Sysprof Exec and it's not being called? Mary Zervos VM Systems Programmer Binghamton University 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: Sysprof Exec in z/vm 4.4
Any chance that a minidisk covering cyl 0 was defined, them deleted? Mary Zervos wrote: Thanks to everyone for their help on Sysprof. I used Mike's suggestion below and it worked like a charm. The new z/vm 4.4 system dust is starting to settle. Anyone game for another question... Yesterday on our new 4.4 system, I was deleting some old users on random packs using Dirmaint while logged onto Maint. Our person who runs Vmbackup was logged on her Vmrmaint account running backups. All the Vmbackup and Vmrmaint mdisks are on the old 230RES pack that we now have attached to the 4.4 system as CP System. The Vmbackup person called me to say that all the mdisks for vmbackup and vmrmaint were empty (she never logged off) and upon checking myself, somehow 230RES was relabeled to SCRTCH. Wow, was that a shocker for me! I immediately restored a backup that I had but am now searching for the reason this happened. Dirmaint? Thanks again for any help. Mary Zervos Binghamton University
Re: Sysprof Exec in z/vm 4.4
Did you bay any chance use DIRMAINT to delete a minidisk that covered cylinder zero of volume 230RES? When DIRMAINT deletes a minidisk, it usua lly has its worker DATAMOVE format the minidisk before deallocating it to prevent the next user from getting data from it. /Tom Kern On Thu, 14 Dec 2006 09:57:06 -0500, Mary Zervos wrote: Anyone game for another question... Yesterday on our new 4.4 system, I was deleting some old users on random packs using Dirmaint while logged onto Maint. Our person who runs Vmbackup was logged on her Vmrmaint account running backups. All the Vmbackup and Vmrmaint mdisks are on the old 230RES pack that we now have attached to the 4.4 system as CP System. The Vmbackup person called me to say that all the mdisks for vmbackup and vmrmaint were empty (she never logged off) and upon checking myself, somehow 230RES was relabeled to SCRTCH. Wow, was that a shocker for me! I immediately restored a backup that I had but am now searching for the reason this happened. Dirmaint?
COMMAND vs. CMS
I have a file containing records that look like this: DELETE USER JOEUSER fpid (TYPE NOCONFIRM This file is read by a pipe and the commands passed to a stage for execution. I have seen and heard the arguments for using COMMAND vs. CMS stages, so I passed the records to COMMAND (as in 'PIPE fid | command | cons'.) Nothing happens as a result. If I change the COMMAND stage to CMS, the commands are acted upon. Funny thing, an appended command of ERASE fid does get executed in either instance. There must be some simple explanation for what is happening, but I must be even simpler. What am I missing? Thanks, Richard Schuh
Re: COMMAND vs. CMS
Richard, What environment is this pipe running in? Clearly, DELETE USER is not a native CMS command. Marty _ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard Sent: Thursday, December 14, 2006 4:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: COMMAND vs. CMS I have a file containing records that look like this: DELETE USER JOEUSER fpid (TYPE NOCONFIRM This file is read by a pipe and the commands passed to a stage for execution. I have seen and heard the arguments for using COMMAND vs. CMS stages, so I passed the records to COMMAND (as in 'PIPE fid | command | cons'.) Nothing happens as a result. If I change the COMMAND stage to CMS, the commands are acted upon. Funny thing, an appended command of ERASE fid does get executed in either instance. There must be some simple explanation for what is happening, but I must be even simpler. What am I missing? Thanks, Richard Schuh
Re: COMMAND vs. CMS
Are you sre the command is written in uppercase? Do you know that you can code CMDCALL before a command so that it generates error messages e.g. PIPE COMMAND ERASE NO FILE A!CONS is silent while PIPE COMMAND CMDCALL ERASE NO FILE A!CONS displays file not found The CMDCALL prefix is especially useful with SFS related commands because the returncode are often not unique then. Kris, IBM Belgium, VM customer support The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU wrote on 2006-12-14 22:08:43: I have a file containing records that look like this: DELETE USER JOEUSER fpid (TYPE NOCONFIRM This file is read by a pipe and the commands passed to a stage for execution. I have seen and heard the arguments for using COMMAND vs. CMS stages, so I passed the records to COMMAND (as in 'PIPE fid | command | cons'.) Nothing happens as a result. If I change the COMMAND stage to CMS, the commands are acted upon. Funny thing, an appended command of ERASE fid does get executed in either instance. There must be some simple explanation for what is happening, but I must be even simpler. What am I missing? Thanks, Richard Schuh
Re: COMMAND vs. CMS
DELETE USER is an SFS Administrator command. From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Marty Zimelis Sent: Thursday, December 14, 2006 1:14 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: COMMAND vs. CMS Richard, What environment is this pipe running in? Clearly, DELETE USER is not a native CMS command. Marty From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard Sent: Thursday, December 14, 2006 4:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: COMMAND vs. CMS I have a file containing records that look like this: DELETE USER JOEUSER fpid (TYPE NOCONFIRM This file is read by a pipe and the commands passed to a stage for execution. I have seen and heard the arguments for using COMMAND vs. CMS stages, so I passed the records to COMMAND (as in 'PIPE fid | command | cons'.) Nothing happens as a result. If I change the COMMAND stage to CMS, the commands are acted upon. Funny thing, an appended command of ERASE fid does get executed in either instance. There must be some simple explanation for what is happening, but I must be even simpler. What am I missing? Thanks, Richard Schuh
Re: COMMAND vs. CMS
DELETE USER is not an EXEC, it is an SFS administrator command. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Thursday, December 14, 2006 1:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: COMMAND vs. CMS The COMMAND stage bypasses the normal search order and won't find EXECs. = Since DELETE USER is not a CMS or CP command it fails. The COMMAND stage= ends when it gets a negative return code if it's secondary output stream = is not connected. Brian Nielsen On Thu, 14 Dec 2006 13:08:43 -0800, Schuh, Richard [EMAIL PROTECTED] wrot= e: I have a file containing records that look like this: DELETE USER JOEUSER fpid (TYPE NOCONFIRM This file is read by a pipe and the commands passed to a stage for execution. I have seen and heard the arguments for using COMMAND vs. CMS= stages, so I passed the records to COMMAND (as in 'PIPE fid | command | cons'.) Nothing happens as a result. If I change the COMMAND stage to CMS, the commands are acted upon. Funny thing, an appended command of ERASE fid does get executed in either instance. There must be some simple explanation for what is happening, but I must be even simpler. What am I missing? Thanks, Richard Schuh
Re: COMMAND vs. CMS
HELP SFSADMIN DELETE From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Marty Zimelis Sent: Thursday, December 14, 2006 1:32 PM To: IBMVM@LISTSERV.UARK.EDU Subject: FW: COMMAND vs. CMS From: Marty Zimelis [mailto:[EMAIL PROTECTED] Sent: Thursday, December 14, 2006 4:14 PM To: 'The IBM z/VM Operating System' Subject: RE: COMMAND vs. CMS Richard, What environment is this pipe running in? Clearly, DELETE USER is not a native CMS command. Well, not for the casual Class G user, anyway Marty From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Schuh, Richard Sent: Thursday, December 14, 2006 4:09 PM To: IBMVM@LISTSERV.UARK.EDU Subject: COMMAND vs. CMS I have a file containing records that look like this: DELETE USER JOEUSER fpid (TYPE NOCONFIRM This file is read by a pipe and the commands passed to a stage for execution. I have seen and heard the arguments for using COMMAND vs. CMS stages, so I passed the records to COMMAND (as in 'PIPE fid | command | cons'.) Nothing happens as a result. If I change the COMMAND stage to CMS, the commands are acted upon. Funny thing, an appended command of ERASE fid does get executed in either instance. There must be some simple explanation for what is happening, but I must be even simpler. What am I missing? Thanks, Richard Schuh
Re: COMMAND vs. CMS
Shot_in_the_dark: ON Not sure of this, because we do not do a lot with SFS here, but could the SFS commands somehow be treated as CP commands? From PIPE HELP COMMAND (in part): ---snip--- The response from the CMS commands is not written to the terminal. The response from each command is buffered until the command ends and is then written to the primary output stream.command does not intercept CP-generated terminal output. ---snip--- Note the last sentence. Shot_in_the_dark: OFF Mike Walter Hewitt Associates Any opinions expressed herein are mine alone and do not necessarily represent the opinions or policies of Hewitt Associates. Schuh, Richard [EMAIL PROTECTED] Sent by: The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU 12/14/2006 04:49 PM Please respond to The IBM z/VM Operating System IBMVM@LISTSERV.UARK.EDU To IBMVM@LISTSERV.UARK.EDU cc Subject Re: COMMAND vs. CMS Irrelevant in this case. Translation is a by-product, not the main thrust, of the command environment. In any event, the commands entered were all upper case. The problem is that either CMS does not recognize SFS administrative commands (and who knows what others) when entered from the Pipelines COMMAND filter, or Pipelines is screwed up. There is no separate command environment for these commands, so they must be CMS commands, and should be so treated, by both Pipelines and CMS. Try the experiment of executing the DELETE USER command from within the address command environment. It will work. -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Richard Feldman (WFF) Sent: Thursday, December 14, 2006 1:53 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: COMMAND vs. CMS This appears to be a SFS admin command. The Command vs CMS is usually in regards to 'address'ing an environment. Addressing Command will issue the command in CMS without translation. Ex. In vanilla CMS if you have a file such as JOEUSER Ofslogfl A In an exec you could issue: 'RENAME JOEUSER Ofslogfl A JOEUSER OFSLOGFL A' this defaults to CMS and will fail because the lower case chars will be translated to upper and the input file will not be found. If you code: Address COMMAND 'RENAME JOEUSER Ofslogfl A JOEUSER OFSLOGFL A' it will succeed because address command passes the exact phrase without trans. Hope that helps, Richard Feldman Senior IT Architect Kelly, Douglas / Westfair Foods Ltd. Ph:(403)291-6339 Fax:(403)291-6585 -Original Message- From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Brian Nielsen Sent: Thursday, December 14, 2006 2:22 PM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: COMMAND vs. CMS The COMMAND stage bypasses the normal search order and won't find EXECs. = Since DELETE USER is not a CMS or CP command it fails. The COMMAND stage= ends when it gets a negative return code if it's secondary output stream = is not connected. Brian Nielsen On Thu, 14 Dec 2006 13:08:43 -0800, Schuh, Richard [EMAIL PROTECTED] wrot= e: I have a file containing records that look like this: DELETE USER JOEUSER fpid (TYPE NOCONFIRM This file is read by a pipe and the commands passed to a stage for execution. I have seen and heard the arguments for using COMMAND vs. CMS= stages, so I passed the records to COMMAND (as in 'PIPE fid | command | cons'.) Nothing happens as a result. If I change the COMMAND stage to CMS, the commands are acted upon. Funny thing, an appended command of ERASE fid does get executed in either instance. There must be some simple explanation for what is happening, but I must be even simpler. What am I missing? Thanks, Richard Schuh 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: COMMAND vs. CMS
On Thursday, 12/14/2006 at 02:49 PST, Schuh, Richard [EMAIL PROTECTED] wrote: Irrelevant in this case. Translation is a by-product, not the main thrust, of the command environment. In any event, the commands entered were all upper case. The problem is that either CMS does not recognize SFS administrative commands (and who knows what others) when entered from the Pipelines COMMAND filter, or Pipelines is screwed up. There is no separate command environment for these commands, so they must be CMS commands, and should be so treated, by both Pipelines and CMS. Try the experiment of executing the DELETE USER command from within the address command environment. It will work. nucxmap delete DMSNXM941I Nucleus extension DELETE is not loaded Ready; execmap delete DMSEXM416W There are no DELETE * EXECs storage resident Ready(00028); listfile delete * * DMSLST002E File not found Ready(00028); type temp file DELETE USER ABC (TYPE NOCONFIRM Ready; pipe temp file a | CMS | cons DMSJDE1139E You are not authorized to issue this command Ready(00076); pipe temp file a | command | cons Ready(00076); The command is executing in either case (fails, of course, but it executes). Naturally my version of Pipes is vanilla-flavored. :-) Alan Altmark z/VM Development IBM Endicott
Re: Sysprof Exec in z/vm 4.4
There is a CYL0_BLK0_CLEANUP setting, and if you set it to YES, it will scratch mdisks that start at cyl 0 too. Or if you have, like we once suffered from, an admin guy who found it more secure to use the option CLEAN on the PURGE or DMDISK commands, overriding the default dirmaint settings, well we lost the same system twice, before we realized that someone else had an userid with fullpack minidisk overlays removed as he was no longer responsible and we were sure we had Dirmaint configured with CYL0_BLK0_CLEANUP=NO .. Ronald van der Laan
Re: COMMAND vs. CMS
Do you have a COMMAND REXX in the mix intercepting the built-in? -- R;
