Re: PDS Lock
Of course superzap does have checking that allows installations to restrict the zapping of VTOC's, so this may (should??) not be available to the OP. Wayne Driscoll Product Developer NOTE: All opinions are strictly my own. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Mike Liberatore Sent: Saturday, October 11, 2008 4:37 PM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: PDS Lock you could zap the FMT-1 dscb for this data set to turn the password bit off of ourse if you want to Scott Rowe wrote: >I'm not sure that is completely true, I remember there being an issue, but I don't remember the details. Not all datasets were protected by RACF (there were no GROUPs or profiles for most HLQs), so that might have had something to do with it. > >Do you have a reference for PASSWORD protection being ignored? I would be interested in trying to recall what the problem was, I think it had something to do with switching sysres, and the PASSWORD dataset not having an entry for a protected dataset. > > > Mark Zelden <[EMAIL PROTECTED]> 10/7/2008 2:50 PM >>> >On Tue, 7 Oct 2008 14:36:29 -0400, Scott Rowe <[EMAIL PROTECTED]> wrote: > > > >>I make it a point NOT to have a PASSWORD dataset on my sysres. I consulted >> >> >at a shiop a few years ago that had one, and it was a PITA, since they were >securing some datasets with password, and others using RACF, believe it or not. > > > >If they had RACF then nothing was being secured with PROTECT. > >-- >Mark Zelden >Sr. Software and Systems Architect - z/OS Team Lead >Zurich North America / Farmers Insurance Group - ZFUS G-ITO >mailto:[EMAIL PROTECTED] >z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ >Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html > > > >Note that my email domain has changed from jo-annstores.com to joann.com. Please update your address book and other records to reflect this change. > >CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. > >-- >For IBM-MAIN subscribe / signoff / archive access instructions, >send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO >Search the archives at http://bama.ua.edu/archives/ibm-main.html > > > > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX error
On Sat, 11 Oct 2008 07:11:12 -0500, Kenneth E Tomiak wrote: >No, you do not need rexx in a comment. It depends. TSO will read them from >SYSEXEC and run them without rexx in the comment. z/OS UNIX Services, in >my limited testing, requires rexx to be lower case where any other >environment/platform could care less about the case. > No -- I've tried a couple case variants and they work. Of course, the case in the invoking shell command must match the case of the UNIX path to the EXEC. However, z/OS UNIX Services requires that the "/* Rexx ..." comment begin in column 1, unlike TSO and CMS. If the comment is indented I get: [EMAIL PROTECTED]:119$ INDENT BPXWI Exec not found [EMAIL PROTECTED]:120$ ... the code explanation is in C.1 "z/OS V1R10.0 Using REXX and z/OS UNIX System Services" __ C.1 BPXWI ___ BPXWI Exec not found Explanation: The REXX program could not be found. System Action: The REXX program is not run. User Response: Check the format of the REXX program ... > As was pointed out, if you get >an IRX message than TSO already figured out it is rexx and the comment is >unnecessary. > Likewise in this case, it appears that exec() recognized the script as Rexx, and then called the Rexx interpreter, which somehow rejected it. I have found no IBM documentation that requires the comment to begin in column 1. Both TSO and CMS accept EXECs with the Rexx comment indented. I reported this in a PMR to IBM, who claimed the problem is impossible to fix. (I regard this as nonsense; IBM merely lacks the determination to make the repair.) -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: PDS Lock
you could zap the FMT-1 dscb for this data set to turn the password bit off of ourse if you want to Scott Rowe wrote: I'm not sure that is completely true, I remember there being an issue, but I don't remember the details. Not all datasets were protected by RACF (there were no GROUPs or profiles for most HLQs), so that might have had something to do with it. Do you have a reference for PASSWORD protection being ignored? I would be interested in trying to recall what the problem was, I think it had something to do with switching sysres, and the PASSWORD dataset not having an entry for a protected dataset. Mark Zelden <[EMAIL PROTECTED]> 10/7/2008 2:50 PM >>> On Tue, 7 Oct 2008 14:36:29 -0400, Scott Rowe <[EMAIL PROTECTED]> wrote: I make it a point NOT to have a PASSWORD dataset on my sysres. I consulted at a shiop a few years ago that had one, and it was a PITA, since they were securing some datasets with password, and others using RACF, believe it or not. If they had RACF then nothing was being secured with PROTECT. -- Mark Zelden Sr. Software and Systems Architect - z/OS Team Lead Zurich North America / Farmers Insurance Group - ZFUS G-ITO mailto:[EMAIL PROTECTED] z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/ Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Note that my email domain has changed from jo-annstores.com to joann.com. Please update your address book and other records to reflect this change. CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Help with deleting datasets which are not cataloged or don't exist.
good catch Scott Rowe wrote: I assume the list below was cut and pasted from ISPF 3.4, in which case I can not imagine how the first entry could not be cataloged, how else could it have been displayed? Howard Rifkind <[EMAIL PROTECTED]> 10/7/2008 4:22 PM >>> Hello all, I'm trying to delete the following datasets: PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL *VSAM* PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.DATA OPSPR2 PDB.SYSPROG.TMON.LMCICS.V22.VTCECNTL.INDEX OPSPR2 For the first one a 'D' states that it isn't cataloged. For the other two a 'D' states that the datasets don't exist. I've tries a delete NVR and a normal delete. Nothing works. Can anyone make some suggestions as how to get these out of the system. An ISPF 3.4 is showing these up. Thanks. _ LEGAL NOTICE Unless expressly stated otherwise, this message is confidential and may be privileged. It is intended for the addressee(s) only. Access to this E-mail by anyone else is unauthorized. If you are not an addressee, any disclosure or copying of the contents of this E-mail or any action taken (or not taken) in reliance on it is unauthorized and may be unlawful. If you are not an addressee, please inform the sender immediately, then delete this message and empty from your trash. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html Note that my email domain has changed from jo-annstores.com to joann.com. Please update your address book and other records to reflect this change. CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains confidential and privileged information intended only for the addressee. If you are not the intended recipient, please be advised that you have received this material in error and that any forwarding, copying, printing, distribution, use or disclosure of the material is strictly prohibited. If you have received this material in error, please (i) do not read it, (ii) reply to the sender that you received the message in error, and (iii) erase or destroy the material. Emails are not secure and can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by email. Thank you. -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX error
Kenneth, That's interesting , have written Rexx since 1984 and always have used the /* rexx */ comment in all my z/OS, VM and Netview clists...wow, Always learning something new...thanks Scott Ford Senior Systems Engineer [p] 678.266.3399 x304[m] 609-346-0399 identityforge.com This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, please notify the sender immediately or let us know at [EMAIL PROTECTED] or [EMAIL PROTECTED], and then delete the original. Any other use of the email by you is prohibited. -Original Message- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth E Tomiak Sent: Saturday, October 11, 2008 8:11 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: REXX error No, you do not need rexx in a comment. It depends. TSO will read them from SYSEXEC and run them without rexx in the comment. z/OS UNIX Services, in my limited testing, requires rexx to be lower case where any other environment/platform could care less about the case. So RExx, REXX, REXx, rexX, reXX, rEXX, rexx in a comment from TSO and read from SYSPROC will all work. Any of those or even not using it from TSO SYSEXEC, and the PC based versions I use, do not need rexx in a comment. As was pointed out, if you get an IRX message than TSO already figured out it is rexx and the comment is unnecessary. On Wed, 8 Oct 2008 01:51:32 -0400, Scott Ford <[EMAIL PROTECTED]> wrote: >Claudio, > >You need a '/* RExx */' line as your first line like below: > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: FIXCAT HOLDDATA
Two points: (1) the only file on the ftp site that has the FIXCAT HOLDs included is the FULL (2 year file). Inclusion of FIXCATs in the other files is still being discussed. (2) SMP/E 3.5 will be able to process the HOLDDATA file that includes FIXCATs. However, unless you run the UPGRADE command against your GLOBAL zone the FIXCAT HOLDs will be ignored and the following message will be produced: GIM58903W SMP/E COULD NOT PROCESS A ++HOLD FIXCAT MCS BECAUSE IT WOULD HAVE MADE A CHANGE TO THE GLOBAL ZONE THAT CANNOT BE PROCESSED COMPLETELY BY PRIOR LEVELS OF SMP/E. USE THE UPGRADE COMMAND TO ALLOW SMP/E TO MAKE SUCH CHANGES. Greg -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX error
Hi,
Is this being done in batch? Foreground TSO? Other (specify)?
We need more context.
I'm use the ex command in BRAS(member) of the my datset see;
VIEW BRATIME.TIME.CHRIST---> my dataset
Command ===>
Name Prompt Size Created
___EX__ BRAS*Edited 34 2008/09/09 -> dataset member
**End**
see my program rexx BRAS:
/* REXX para mostrar o dia da semana que cai o natal. BY CLAUDIO MARCIO */
/***/
/* Say 'Calculate Christmas day in year ?' */
Say 'Este programa informa em que dia da semana foi ou sera o Natal',
'em determinado ano, que ano quer saber ?'
pull year
do until answer \= "S"
if year = "" then year = right(date(),4)
dec25 = date("B",year"1225","S")//7
select
when dec25 = 0 then day = "Segunda-feira"
when dec25 = 1 then day = "Terca-feira"
when dec25 = 2 then day = "Quarta-feira"
when dec25 = 3 then day = "Quinta-feira"
when dec25 = 4 then day = "Sexta-feira"
when dec25 = 5 then day = "Sabado"
otherwise day = "Domingo"
end
if year < right(date(),4) then
say 'Em 'year', o natal foi 'day
else
say 'Em 'year', o natal sera 'day
say 'Deseja saber mais algum ano ? (s/n)'
pull answer
if answer = 'S' then
Say 'Vamos la entao, qual outro ano voce gostaria de saber!!'
else
do
say 'BYE! BYE!'
leave
end
pull year
end
exit
regards
- Original Message -
From: "Kenneth E Tomiak" <[EMAIL PROTECTED]>
Newsgroups: bit.listserv.ibm-main
To:
Sent: Saturday, October 11, 2008 9:05 AM
Subject: Re: REXX error
I put my money on he is changing it. To get the first error I did a cut and
paste of his code and changed the leading x40 to x20 and got the same
first
error. It then works. Changing anything outside the apostrophes caused the
same problem. Thus his second error is coming from somewhere else.
Why would you expect someone who can not code a simple say statement to
turn on trace and find his own problems when he has the listserv to do his
work?
On Wed, 8 Oct 2008 09:04:52 -0500, Paul Gilmartin <[EMAIL PROTECTED]>
wrote:
Date: Tue, 7 Oct 2008 02:12:59 -0300
Content-Type: text/plain
when I run my exec REXX the error appears:
1 +++ ?
IRX0013I Error running BRAS, line 1: Invalid character in program
... clearly a Rexx message. Is Claudio changing the conditions of the
problem without informing us? Or is his script being interpreted as a
CLIST, or open code in SYSTSIN, which contains a token which causes an
invalid Rexx exec to be invoked?
Is this being done in batch? Foreground TSO? Other (specify)? We
need more context.
-- gil
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX error
correcting... a debug command? regards - Original Message - From: "Claudio Marcio" <[EMAIL PROTECTED]> To: "IBM Mainframe Discussion List" Sent: Saturday, October 11, 2008 10:14 AM Subject: Re: REXX error How do on trace to find my problems and how see this listserv?? The TSO has a degug command? regards - Original Message - From: "Kenneth E Tomiak" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: Sent: Saturday, October 11, 2008 9:05 AM Subject: Re: REXX error I put my money on he is changing it. To get the first error I did a cut and paste of his code and changed the leading x40 to x20 and got the same first error. It then works. Changing anything outside the apostrophes caused the same problem. Thus his second error is coming from somewhere else. Why would you expect someone who can not code a simple say statement to turn on trace and find his own problems when he has the listserv to do his work? On Wed, 8 Oct 2008 09:04:52 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote: Date: Tue, 7 Oct 2008 02:12:59 -0300 Content-Type: text/plain when I run my exec REXX the error appears: 1 +++ ? IRX0013I Error running BRAS, line 1: Invalid character in program ... clearly a Rexx message. Is Claudio changing the conditions of the problem without informing us? Or is his script being interpreted as a CLIST, or open code in SYSTSIN, which contains a token which causes an invalid Rexx exec to be invoked? Is this being done in batch? Foreground TSO? Other (specify)? We need more context. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX error
How do on trace to find my problems and how see this listserv?? The TSO has a degug command? regards - Original Message - From: "Kenneth E Tomiak" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: Sent: Saturday, October 11, 2008 9:05 AM Subject: Re: REXX error I put my money on he is changing it. To get the first error I did a cut and paste of his code and changed the leading x40 to x20 and got the same first error. It then works. Changing anything outside the apostrophes caused the same problem. Thus his second error is coming from somewhere else. Why would you expect someone who can not code a simple say statement to turn on trace and find his own problems when he has the listserv to do his work? On Wed, 8 Oct 2008 09:04:52 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote: Date: Tue, 7 Oct 2008 02:12:59 -0300 Content-Type: text/plain when I run my exec REXX the error appears: 1 +++ ? IRX0013I Error running BRAS, line 1: Invalid character in program ... clearly a Rexx message. Is Claudio changing the conditions of the problem without informing us? Or is his script being interpreted as a CLIST, or open code in SYSTSIN, which contains a token which causes an invalid Rexx exec to be invoked? Is this being done in batch? Foreground TSO? Other (specify)? We need more context. -- gil -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX error
No, you do not need rexx in a comment. It depends. TSO will read them from SYSEXEC and run them without rexx in the comment. z/OS UNIX Services, in my limited testing, requires rexx to be lower case where any other environment/platform could care less about the case. So RExx, REXX, REXx, rexX, reXX, rEXX, rexx in a comment from TSO and read from SYSPROC will all work. Any of those or even not using it from TSO SYSEXEC, and the PC based versions I use, do not need rexx in a comment. As was pointed out, if you get an IRX message than TSO already figured out it is rexx and the comment is unnecessary. On Wed, 8 Oct 2008 01:51:32 -0400, Scott Ford <[EMAIL PROTECTED]> wrote: >Claudio, > >You need a '/* RExx */' line as your first line like below: > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: REXX error
I put my money on he is changing it. To get the first error I did a cut and paste of his code and changed the leading x40 to x20 and got the same first error. It then works. Changing anything outside the apostrophes caused the same problem. Thus his second error is coming from somewhere else. Why would you expect someone who can not code a simple say statement to turn on trace and find his own problems when he has the listserv to do his work? On Wed, 8 Oct 2008 09:04:52 -0500, Paul Gilmartin <[EMAIL PROTECTED]> wrote: > > Date: Tue, 7 Oct 2008 02:12:59 -0300 > Content-Type: text/plain >when I run my exec REXX the error appears: > 1 +++ ? >IRX0013I Error running BRAS, line 1: Invalid character in program > >... clearly a Rexx message. Is Claudio changing the conditions of the >problem without informing us? Or is his script being interpreted as a >CLIST, or open code in SYSTSIN, which contains a token which causes an >invalid Rexx exec to be invoked? > >Is this being done in batch? Foreground TSO? Other (specify)? We >need more context. > >-- gil > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
Re: Fwd: DB2 for z/OS WLM stored procedure setup
I have been taking the parms out of WLM because I have them in the PROC and they get found and used just fine. z/OS 1.7 and 1.9. Much easier to change in the PROC anyway. On Fri, 10 Oct 2008 16:31:19 +0100, Jim McAlpine <[EMAIL PROTECTED]> wrote: >>Problem sorted. In my WLM application environment definition I hadn't >specified anything in the "start parameters" field. I figured that if the >information was in the proc then it wasn't required here. Anyhow I added >"DB2SSN=&IWMSSNM,APPLENV=JDBCENV" and bingo it worked. Procedure not found >was a very strange symptom though. > >Jim McAlpine > -- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
