date:20090306

On Fri, 6 Mar 2009 12:17:49 +0800, Tommy Tsui  wrote:

>  Is there any RACF password rule that can validate  the password
>cannot be a part of USERID? or only write a user exit to implement it?

You would probably need an exit to do that.  You can find a sample exit on
the RACF downloads page
(http://www-03.ibm.com/servers/eserver/zseries/zos/racf/goodies.html ) that
should simplify that.  See REXXPWEXIT.  It works on z/OS R10 and later, and
provides an ICHPWX01 exit that invokes a REXX exec via System REXX, and a
sample REXX exec that you can tailor easily.

-- 
  Walt Farrell, CISSP
  IBM STSM, z/OS Security Design

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Jousma, David

Yikes,

Should I be scared of this?  Externalizing the password rules in REXX?
Seems to make it too easy to "collect" passwords.  

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Walt Farrell
Sent: Friday, March 06, 2009 7:58 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

On Fri, 6 Mar 2009 12:17:49 +0800, Tommy Tsui 
wrote:

>  Is there any RACF password rule that can validate  the password
>cannot be a part of USERID? or only write a user exit to implement it?

You would probably need an exit to do that.  You can find a sample exit
on
the RACF downloads page
(http://www-03.ibm.com/servers/eserver/zseries/zos/racf/goodies.html )
that
should simplify that.  See REXXPWEXIT.  It works on z/OS R10 and later,
and
provides an ICHPWX01 exit that invokes a REXX exec via System REXX, and
a
sample REXX exec that you can tailor easily.

-- 
  Walt Farrell, CISSP
  IBM STSM, z/OS Security Design

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Should TIME LINKAGE=SYSTEM support a PLIST above the bar?

2009-03-06 Thread Steven Partlow

On Thu, 5 Mar 2009 10:31:55 -0600, Walt Farrell  wrote:
...
>According to the book, only a limited set of MVS assembler programming
>services support invocation in 64-bit addressing mode, and only a more
>limited set of the services support parameters above the bar.
>
>See
>http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A990/1.2?SHELF=EZ2ZO10L&DT=20080601235844&CASE=
>or http://preview.tinyurl.com/b9alno
>-- Walt


That list could use some updating. Some other system services that support
parameters above the bar include: IARST64, IARCP64, ITTWRITE, ISGENQ,
ISGQUERY, ISGADMIN, ISGLCR64, ISGLOB64, ISGLRE64, ISGLPR64, ISGLPB64.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Can TOD (STCKE) be compressed into 12 bytes

2009-03-06 Thread Don Williams

IBM has already implied that the TOD register is intended to be a programming 
interface by stating in the POP manual:

“13. Uniqueness of TOD-clock values can be extended to apply to processors 
in separate configurations by including a configuration identification in the 
TOD 
programmable field.”

IBM should state (in z/OS documentation) that z/OS guarantees a unique 
value in each register of a sysplex (as suggested in the POP manual), 
however, the particular value is not a programming interface, only that the 
value will be unique within a sysplex. 

IBM should state in other operating system (z/VM, VSE, etc.) documentation, 
how it sets or does not set that register.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

On Fri, 6 Mar 2009 08:05:30 -0500, Jousma, David  wrote:

>Should I be scared of this?  Externalizing the password rules in REXX?
>Seems to make it too easy to "collect" passwords.

System REXX execs run APF-authorized, and the libraries containing them must
be protected the same way as any other APF-authorized library.

If someone could update that REXX exec to collect passwords, he could also
update an assembler exit to collect them, too.  True, it requires a little
more knowledge to create a program in assembler language that would collect
a password and open a data set to record it, but that knowledge is wide
spread enough that it's really the same concern whether you deal with REXX
or assembler exits.

So, no, you should not be scared of it.

-- 
  Walt Farrell, CISSP
  IBM STSM, z/OS Security Design

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Should TIME LINKAGE=SYSTEM support a PLIST above the bar?

On Fri, 6 Mar 2009 07:06:08 -0600, Steven Partlow  wrote:

>On Thu, 5 Mar 2009 10:31:55 -0600, Walt Farrell  wrote:
>...
>>According to the book, only a limited set of MVS assembler programming
>>services support invocation in 64-bit addressing mode, and only a more
>>limited set of the services support parameters above the bar.
>>
>>See
>>http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/IEA2A990/1.2?SHELF=EZ2ZO10L&DT=20080601235844&CASE=
>>or http://preview.tinyurl.com/b9alno
>>-- Walt
>
>
>That list could use some updating. Some other system services that support
>parameters above the bar include: IARST64, IARCP64, ITTWRITE, ISGENQ,
>ISGQUERY, ISGADMIN, ISGLCR64, ISGLOB64, ISGLRE64, ISGLPR64, ISGLPB64.
>

Thanks for mentioning it.  I presume you'll also submit the Reader's Comment
to get it updated :-)

-- 
  Walt

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Can TOD (STCKE) be compressed into 12 bytes

On Fri, 6 Mar 2009 07:43:26 -0600, Don Williams  wrote:

>IBM has already implied that the TOD register is intended to be a programming
>interface by stating in the POP manual:
>
>13. Uniqueness of TOD-clock values can be extended to apply to processors
>in separate configurations by including a configuration identification in
the TOD
>programmable field.
>
>IBM should state (in z/OS documentation) that z/OS guarantees a unique
>value in each register of a sysplex (as suggested in the POP manual),
>however, the particular value is not a programming interface, only that the
>value will be unique within a sysplex.

There are many hardware architectural features described in the PoP that
z/OS does not consider programming interfaces for programs running on z/OS.
 Finding and documenting all of them appropriately as "not a programming
interface" would require a lot of work, I think.

-- 
  Walt

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Can TOD (STCKE) be compressed into 12 bytes

2009-03-06 Thread Anne & Lynn Wheeler

The following message is a courtesy copy of an article
that has been posted to bit.listserv.ibm-main as well.

wfarr...@us.ibm.com (Walt Farrell) writes:
> There are many hardware architectural features described in the PoP that
> z/OS does not consider programming interfaces for programs running on z/OS.
>  Finding and documenting all of them appropriately as "not a programming
> interface" would require a lot of work, I think.

A lot less than before (360) POP was moved into CMS script file. The 
original reason was the ease of editing/dealing with the text.

a motivation was that the POP was subset of the architecture "red book"
(from it being distributed in a "red" 3-ring binder). As CMS script
file, it allowed pertinent information to be kept together (for easy
edit & management), but CMS command line option controlled whether the
POP subset was printed or the full architecture manual was printed.

-- 
40+yrs virtualization experience (since Jan68), online at home since Mar70

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Hal Merritt

IMHO: exits as a subspecies are evil critters. They become an ongoing 
maintenance challenge and tend to attract unwelcome attention from auditors. 
Exits are hard to write, hard to stress test, and introduce a level of risk. 
You need extraordinary measures in place to protect the code. 

On the well proven fact that there is no software that is completely bug free, 
why would you want to introduce -more- bugs into your most sacred of processes: 
authentication? 

There is another pretty interesting argument that as the complexity of your 
solution package increases, so do the opportunities for holes. Perhaps put 
there intentionally (the largest risk is internal) or intentionally (bugs).  

I once worked in an exit happy shop. Getting the exits updated and tested 
tended to be the single biggest bottleneck in rolling out new operating system 
levels.  

Of course, if you have a compelling business/technical need, then lock and 
load. 

My humble $0.02 US (before taxes). 

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of 
Jousma, David
Sent: Friday, March 06, 2009 7:06 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

Yikes,

Should I be scared of this?  Externalizing the password rules in REXX?
Seems to make it too easy to "collect" passwords.  

_
Dave Jousma
Assistant Vice President, Mainframe Services
david.jou...@53.com
1830 East Paris, Grand Rapids, MI  49546 MD RSCB1G
p 616.653.8429
f 616.653.8497

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
Behalf Of Walt Farrell
Sent: Friday, March 06, 2009 7:58 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

On Fri, 6 Mar 2009 12:17:49 +0800, Tommy Tsui 
wrote:

>  Is there any RACF password rule that can validate  the password
>cannot be a part of USERID? or only write a user exit to implement it?

You would probably need an exit to do that.  You can find a sample exit
on
the RACF downloads page
(http://www-03.ibm.com/servers/eserver/zseries/zos/racf/goodies.html )
that
should simplify that.  See REXXPWEXIT.  It works on z/OS R10 and later,
and
provides an ICHPWX01 exit that invokes a REXX exec via System REXX, and
a
sample REXX exec that you can tailor easily.

-- 
  Walt Farrell, CISSP
  IBM STSM, z/OS Security Design

This e-mail transmission contains information that is confidential and may be 
privileged.   It is intended only for the addressee(s) named above. If you 
receive this e-mail in error, please do not read, copy or disseminate it in any 
manner. If you are not the intended recipient, any disclosure, copying, 
distribution or use of the contents of this information is prohibited. Please 
reply to the message immediately by informing the sender that the message was 
misdirected. After replying, please erase it from your computer system. Your 
assistance in correcting this error is appreciated.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

How to use CSI Catalog Search Interface

2009-03-06 Thread Lizette Koehler

I am cross posting this to IBM Main incase there are folkes out there that use 
CSI more than the TSO REXX group does.

Lizette



>
>I have been working with the sample in SYS1.SAMPLIB as well as Mark Zelden's 
>version called catsearch.  I want to include the information on High RBA on 
>VSAM data sets.  When I add in what I think is correct I get garbage.  I am 
>reading Appendix C in the DFSMS Managing Catalogs manual which is where it 
>talks about the CSI.
>
>Has anyone written a CSI in REXX and can help me over come my short comings in 
>coding this?
>
>I set up the following code (excerpt)
>
>CSIRESRV = SUBSTR(' ',1,1)  /*   CLEAR RESERVE CHARACTER */
>CSINUMEN = '0004'X  /*   INIT NUMBER OF FIELDS   */
>XHARBA   = 'XHARBA  '  
>XHARBADS = 'XHARBADS'  
>XHKRBA   = 'XHKRBA  '  
>VOLSER   = 'VOLSER  '  
>CSIFLD1  = VOLSER || XHARBA || XHARBADS || XHKRBA  
> //
> /*  */
> /*  BUILD THE SELECTION CRITERIA FIELDS PART OF PARAMETER LIST  */
> /*  */
> //
>CSIOPTS  = CSICLDI  || CSIRESUM || CSIS1CAT || CSIRESRV
> 
>CSIFIELD = CSIFILTK || CSICATNM || CSIRESNM || CSIDTYPS || CSIOPTS 
>CSIFIELD = CSIFIELD || CSINUMEN || CSIFLD1 
>   
>
>Then I issue the 
>
>ADDRESS LINKPGM 'IGGCSI00  MODRSNRC  CSIFIELD  DWORK'   
>RESUME = SUBSTR(CSIFIELD,150,1)/* GET RESUME FLAG FOR NEXT LOOP */  
>USEDLEN = C2D(SUBSTR(DWORK,9,4))   /* GET AMOUNT OF WORK AREA USED  */  
>POS1=15/* STARTING POSITION */  
>
>Then I loop through.  For some reason the base code without my changes works 
>(it only goes after the VOLSER).  However with the additions of the XHARBA, 
>XHKRBA and XHARBADS, and adjusting the CSINUNEN from '0001'x to '0004'x it is 
>not doing what I want.  All fields are 8 chars long padded with blanks on the 
>right.
>
>If someone would have some samples of code to share I would be appreciative.
>
>Lizette

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: How to use CSI Catalog Search Interface

Just at first glance...

I know the requested filed names must be 8 bytes or padded. 
The sample and my exec have:

CSIFLD1= SUBSTR('VOLSER',1,8) 

But you can use:

CSIFLD1  = 'VOLSER  '|| 'XHARBA  '|| 'XHARBADS' || 'XHKRBA  ' 

I don't know if that is your only problem.

--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zel...@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html



On Fri, 6 Mar 2009 10:01:33 -0500, Lizette Koehler 
wrote:

>I am cross posting this to IBM Main incase there are folkes out there that
use CSI more than the TSO REXX group does.
>
>Lizette
>
>
>
>>
>>I have been working with the sample in SYS1.SAMPLIB as well as Mark
Zelden's version called catsearch.  I want to include the information on
High RBA on VSAM data sets.  When I add in what I think is correct I get
garbage.  I am reading Appendix C in the DFSMS Managing Catalogs manual
which is where it talks about the CSI.
>>
>>Has anyone written a CSI in REXX and can help me over come my short
comings in coding this?
>>
>>I set up the following code (excerpt)
>>
>>CSIRESRV = SUBSTR(' ',1,1)  /*   CLEAR RESERVE CHARACTER */
>>CSINUMEN = '0004'X  /*   INIT NUMBER OF FIELDS   */
>>XHARBA   = 'XHARBA  '
>>XHARBADS = 'XHARBADS'
>>XHKRBA   = 'XHKRBA  '
>>VOLSER   = 'VOLSER  '
>>CSIFLD1  = VOLSER || XHARBA || XHARBADS || XHKRBA
>> //
>> /*  */
>> /*  BUILD THE SELECTION CRITERIA FIELDS PART OF PARAMETER LIST  */
>> /*  */
>> //
>>CSIOPTS  = CSICLDI  || CSIRESUM || CSIS1CAT || CSIRESRV
>>CSIFIELD = CSIFILTK || CSICATNM || CSIRESNM || CSIDTYPS || CSIOPTS
>>CSIFIELD = CSIFIELD || CSINUMEN || CSIFLD1
>>
>>
>>Then I issue the
>>
>>ADDRESS LINKPGM 'IGGCSI00  MODRSNRC  CSIFIELD  DWORK'
>>RESUME = SUBSTR(CSIFIELD,150,1)/* GET RESUME FLAG FOR NEXT LOOP */
>>USEDLEN = C2D(SUBSTR(DWORK,9,4))   /* GET AMOUNT OF WORK AREA USED  */
>>POS1=15/* STARTING POSITION */
>>
>>Then I loop through.  For some reason the base code without my changes
works (it only goes after the VOLSER).  However with the additions of the
XHARBA, XHKRBA and XHARBADS, and adjusting the CSINUNEN from '0001'x to
'0004'x it is not doing what I want.  All fields are 8 chars long padded
with blanks on the right.
>>
>>If someone would have some samples of code to share I would be appreciative.
>>
>>Lizette
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: How to use CSI Catalog Search Interface

Ooops. Sorry  I didn't notice you already padded those fields.  

I said it was a quick glance. :-)Off to my meeting now...

Mark



On Fri, 6 Mar 2009 09:13:51 -0600, Mark Zelden  wrote:

>Just at first glance...
>
>I know the requested filed names must be 8 bytes or padded.
>The sample and my exec have:
>
>CSIFLD1= SUBSTR('VOLSER',1,8)
>
>But you can use:
>
>CSIFLD1  = 'VOLSER  '|| 'XHARBA  '|| 'XHARBADS' || 'XHKRBA  '
>
>I don't know if that is your only problem.
>
>--
>Mark Zelden
>Sr. Software and Systems Architect - z/OS Team Lead
>Zurich North America / Farmers Insurance Group - ZFUS G-ITO
>mailto:mark.zel...@zurichna.com
>z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
>Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html
>
>
>
>On Fri, 6 Mar 2009 10:01:33 -0500, Lizette Koehler 
>wrote:
>
>>I am cross posting this to IBM Main incase there are folkes out there that
>use CSI more than the TSO REXX group does.
>>
>>Lizette
>>
>>
>>
>>>
>>>I have been working with the sample in SYS1.SAMPLIB as well as Mark
>Zelden's version called catsearch.  I want to include the information on
>High RBA on VSAM data sets.  When I add in what I think is correct I get
>garbage.  I am reading Appendix C in the DFSMS Managing Catalogs manual
>which is where it talks about the CSI.
>>>
>>>Has anyone written a CSI in REXX and can help me over come my short
>comings in coding this?
>>>
>>>I set up the following code (excerpt)
>>>
>>>CSIRESRV = SUBSTR(' ',1,1)  /*   CLEAR RESERVE CHARACTER */
>>>CSINUMEN = '0004'X  /*   INIT NUMBER OF FIELDS   */
>>>XHARBA   = 'XHARBA  '
>>>XHARBADS = 'XHARBADS'
>>>XHKRBA   = 'XHKRBA  '
>>>VOLSER   = 'VOLSER  '
>>>CSIFLD1  = VOLSER || XHARBA || XHARBADS || XHKRBA
>>> //
>>> /*  */
>>> /*  BUILD THE SELECTION CRITERIA FIELDS PART OF PARAMETER LIST  */
>>> /*  */
>>> //
>>>CSIOPTS  = CSICLDI  || CSIRESUM || CSIS1CAT || CSIRESRV
>>>CSIFIELD = CSIFILTK || CSICATNM || CSIRESNM || CSIDTYPS || CSIOPTS
>>>CSIFIELD = CSIFIELD || CSINUMEN || CSIFLD1
>>>
>>>
>>>Then I issue the
>>>
>>>ADDRESS LINKPGM 'IGGCSI00  MODRSNRC  CSIFIELD  DWORK'
>>>RESUME = SUBSTR(CSIFIELD,150,1)/* GET RESUME FLAG FOR NEXT LOOP */
>>>USEDLEN = C2D(SUBSTR(DWORK,9,4))   /* GET AMOUNT OF WORK AREA USED  */
>>>POS1=15/* STARTING POSITION */
>>>
>>>Then I loop through.  For some reason the base code without my changes
>works (it only goes after the VOLSER).  However with the additions of the
>XHARBA, XHKRBA and XHARBADS, and adjusting the CSINUNEN from '0001'x to
>'0004'x it is not doing what I want.  All fields are 8 chars long padded
>with blanks on the right.
>>>
>>>If someone would have some samples of code to share I would be appreciative.
>>>
>>>Lizette
>>
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: How to use CSI Catalog Search Interface

Unless you completely changed the code that loops though the work area,
what you changed will not work.  

Have a really good look at CSI user guide in  z/OS DFSMS Managing 
Catalogs appendix C section 5:

C.5 Return Work Area Format

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zel...@zurichna.com
z/OS Systems Programming expert at http://expertanswercenter.techtarget.com/
Mark's MVS Utilities: http://home.flash.net/~mzelden/mvsutil.html


On Fri, 6 Mar 2009 10:01:33 -0500, Lizette Koehler 
wrote:

>I am cross posting this to IBM Main incase there are folkes out there that
use CSI more than the TSO REXX group does.
>
>Lizette
>
>
>
>>
>>I have been working with the sample in SYS1.SAMPLIB as well as Mark
Zelden's version called catsearch.  I want to include the information on
High RBA on VSAM data sets.  When I add in what I think is correct I get
garbage.  I am reading Appendix C in the DFSMS Managing Catalogs manual
which is where it talks about the CSI.
>>
>>Has anyone written a CSI in REXX and can help me over come my short
comings in coding this?
>>
>>I set up the following code (excerpt)
>>
>>CSIRESRV = SUBSTR(' ',1,1)  /*   CLEAR RESERVE CHARACTER */
>>CSINUMEN = '0004'X  /*   INIT NUMBER OF FIELDS   */
>>XHARBA   = 'XHARBA  '
>>XHARBADS = 'XHARBADS'
>>XHKRBA   = 'XHKRBA  '
>>VOLSER   = 'VOLSER  '
>>CSIFLD1  = VOLSER || XHARBA || XHARBADS || XHKRBA
>> //
>> /*  */
>> /*  BUILD THE SELECTION CRITERIA FIELDS PART OF PARAMETER LIST  */
>> /*  */
>> //
>>CSIOPTS  = CSICLDI  || CSIRESUM || CSIS1CAT || CSIRESRV
>>CSIFIELD = CSIFILTK || CSICATNM || CSIRESNM || CSIDTYPS || CSIOPTS
>>CSIFIELD = CSIFIELD || CSINUMEN || CSIFLD1
>>
>>
>>Then I issue the
>>
>>ADDRESS LINKPGM 'IGGCSI00  MODRSNRC  CSIFIELD  DWORK'
>>RESUME = SUBSTR(CSIFIELD,150,1)/* GET RESUME FLAG FOR NEXT LOOP */
>>USEDLEN = C2D(SUBSTR(DWORK,9,4))   /* GET AMOUNT OF WORK AREA USED  */
>>POS1=15/* STARTING POSITION */
>>
>>Then I loop through.  For some reason the base code without my changes
works (it only goes after the VOLSER).  However with the additions of the
XHARBA, XHKRBA and XHARBADS, and adjusting the CSINUNEN from '0001'x to
'0004'x it is not doing what I want.  All fields are 8 chars long padded
with blanks on the right.
>>
>>If someone would have some samples of code to share I would be appreciative.
>>
>>Lizette
>
>--
>For IBM-MAIN subscribe / signoff / archive access instructions,
>send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Insert tapes in a TS3500 without a barcode

2009-03-06 Thread Lopez, Sharon

We are trying to insert a server/pak tape 3592 into our TS3500 library, and the 
accessor is picking it up without a barcode.  We followed the manual (redbook), 
 and the accessor should not pick it up.  Do we need to set something in the 
box?  Thank you.


Inserting cartridges without a barcode label
You might receive cartridges from a software vendor, another company, or even 
from IBM
that have standard label (SL) formats but no barcode labels. This special 
situation needs a
particular procedure. The following example describes the insertion of a 
cartridge with an SL
of YX0100:
1. First, you must verify that this VOLSER is not defined within a VOLSER range 
in the
TS3500.
2. Insert the cartridge in the entry station. The accessor will not pick the 
cartridge because of
the missing barcode.
3. Use your Web specialist function to select Manage Cartridges → I/O Station.
You will see only one cartridge with unknown status.
4. Select the cartridge and select Fix Unknown Volume Serial.
5. Enter VOLSER=YX0100 and the type (JA, JJ, and so forth).


Sharon Lopez
Enterprise z/OS Systems Programmer
State of North Carolina
Office of Information Technology Services
919-754-6432 Office
919-398-8638 Cell
919-850-2854  Fax
919-754-6000 ITS Service Desk

sharon.lo...@its.nc.gov
http://www.its.state.nc.us

E-mail correspondence to and from this address may be subject to the North 
Carolina Public Records Law and may be disclosed to third parties by authorized 
state officials
-

Re: RACF password & id checking

On Fri, 6 Mar 2009 08:48:18 -0600, Hal Merritt  wrote:

>IMHO: exits as a subspecies are evil critters. They become an ongoing
maintenance challenge and tend to attract unwelcome attention from auditors.
Exits are hard to write, hard to stress test, and introduce a level of risk.
You need extraordinary measures in place to protect the code.
>
>On the well proven fact that there is no software that is completely bug
free, why would you want to introduce -more- bugs into your most sacred of
processes: authentication?
>
>There is another pretty interesting argument that as the complexity of your
solution package increases, so do the opportunities for holes. Perhaps put
there intentionally (the largest risk is internal) or intentionally (bugs).
>
>I once worked in an exit happy shop. Getting the exits updated and tested
tended to be the single biggest bottleneck in rolling out new operating
system levels.
>
>Of course, if you have a compelling business/technical need, then lock and
load.

Those are some of the reasons that we provided the REXX part of the exit,
too, with code that implements some commonly requested functions.  Ideally
all you have to do is set some switches to enable the functions we've
already written.

-- 
  Walt Farrell, CISSP
  IBM STSM, z/OS Security Design

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Can TOD (STCKE) be compressed into 12 bytes

2009-03-06 Thread Don Williams

Yes, it would take a lot of work to document how z/OS (or any other 
operating system) utilizes various hardware features. However, IBM customer’s 
are on shaky ground, if they build systems based on undocumented features 
or functions. In the long run, it is probably in IBM’s best interest to 
document 
features or functions they know that their customer base is using or wants to 
use.

Since IBM does not document that z/OS guarantees that the extended TOD 
clock values will be unique across a sysplex, I would not recommend that 
someone design their software to depend on it being unique. Their programs 
should be prepared to handle duplicate values.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: 3490E cartridges

2009-03-06 Thread Paul Gilmartin

On Fri, 6 Mar 2009 12:02:23 +0100, R.S. wrote:

>Schwarz, Barry A wrote:
>> Aren't beliefs a wonderful thing.
>>
>> Since one customer is still using 3270 style dumb terminals exclusively, ...
>
>BTW: Even "coax network" can connect CD to a mainframe. You need PC with
>CD and coax card. It can be old HMC - older OS/2 based HMCs did have both.
>
FSVO "connect".  Does the CD appear to the mainframe as a storage
device/subsystem, or is the connection limited to file transfers
initiated by the PC.

Of course, one might run an NFS server on the PC and export the CD.
But that's late 20th century technology, likely not appealing to
the cited customer.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Tommy Tsui

I saw the REXX code and it's quite simple. Just turn it on...I will try it ..
thanks all of your help

On Fri, Mar 6, 2009 at 11:46 PM, Walt Farrell  wrote:
> On Fri, 6 Mar 2009 08:48:18 -0600, Hal Merritt  wrote:
>
>>IMHO: exits as a subspecies are evil critters. They become an ongoing
> maintenance challenge and tend to attract unwelcome attention from auditors.
> Exits are hard to write, hard to stress test, and introduce a level of risk.
> You need extraordinary measures in place to protect the code.
>>
>>On the well proven fact that there is no software that is completely bug
> free, why would you want to introduce -more- bugs into your most sacred of
> processes: authentication?
>>
>>There is another pretty interesting argument that as the complexity of your
> solution package increases, so do the opportunities for holes. Perhaps put
> there intentionally (the largest risk is internal) or intentionally (bugs).
>>
>>I once worked in an exit happy shop. Getting the exits updated and tested
> tended to be the single biggest bottleneck in rolling out new operating
> system levels.
>>
>>Of course, if you have a compelling business/technical need, then lock and
> load.
>
> Those are some of the reasons that we provided the REXX part of the exit,
> too, with code that implements some commonly requested functions.  Ideally
> all you have to do is set some switches to enable the functions we've
> already written.
>
> --
>  Walt Farrell, CISSP
>  IBM STSM, z/OS Security Design
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: How to use CSI Catalog Search Interface

2009-03-06 Thread Richard Pace

On Friday 06 March 2009, Lizette Koehler wrote:
> I am cross posting this to IBM Main incase there are folkes out there that
> use CSI more than the TSO REXX group does.
>
> Lizette
>
> >I have been working with the sample in SYS1.SAMPLIB as well as Mark
> > Zelden's version called catsearch.  I want to include the information on
> > High RBA on VSAM data sets.  When I add in what I think is correct I get
> > garbage.  I am reading Appendix C in the DFSMS Managing Catalogs manual
> > which is where it talks about the CSI.
> >
I suggest you dump the work area after the call to see what it looks like.  I 
have found the returned work area hard to visualize from just the 
description, esp. with multiple entries.  Also, if fields names do not apply 
to a particualar data set, I believe the field values contain all x'ff's.  
i.e. XHARBA is not a valid field for non-vsam, so its returned value will be 
x''.
-- 
Regards,
Richard

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: How to use CSI Catalog Search Interface

2009-03-06 Thread Lizette Koehler

Thanks for the response.

I am working with just VSAM at this time.  However, I will enhance the code to 
verify if it vsam or non-vsam and then call the appropriate routines (either 
IGGCSI00 or LISTDSI).

Lizette


>On Friday 06 March 2009, Lizette Koehler wrote:
>> I am cross posting this to IBM Main incase there are folkes out there that
>> use CSI more than the TSO REXX group does.
>>
>> Lizette
>>
>> >I have been working with the sample in SYS1.SAMPLIB as well as Mark
>> > Zelden's version called catsearch.  I want to include the information on
>> > High RBA on VSAM data sets.  When I add in what I think is correct I get
>> > garbage.  I am reading Appendix C in the DFSMS Managing Catalogs manual
>> > which is where it talks about the CSI.
>> >
>I suggest you dump the work area after the call to see what it looks like.  I 
>have found the returned work area hard to visualize from just the 
>description, esp. with multiple entries.  Also, if fields names do not apply 
>to a particualar data set, I believe the field values contain all x'ff's.  
>i.e. XHARBA is not a valid field for non-vsam, so its returned value will be 
>x''.
>-- 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

On Sat, 7 Mar 2009 00:12:16 +0800, Tommy Tsui  wrote:

>I saw the REXX code and it's quite simple. Just turn it on...I will try it ..
>thanks all of your help

Do remember that it works only on z/OS R10 and later, though.

-- 
  Walt Farrell, CISSP
  IBM STSM, z/OS Security Design

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: 3490E cartridges

2009-03-06 Thread R.S.


Paul Gilmartin wrote:

On Fri, 6 Mar 2009 12:02:23 +0100, R.S. wrote:


Schwarz, Barry A wrote:

Aren't beliefs a wonderful thing.

Since one customer is still using 3270 style dumb terminals exclusively, ...

BTW: Even "coax network" can connect CD to a mainframe. You need PC with
CD and coax card. It can be old HMC - older OS/2 based HMCs did have both.


FSVO "connect".  Does the CD appear to the mainframe as a storage
device/subsystem, or is the connection limited to file transfers
initiated by the PC.

Of course, one might run an NFS server on the PC and export the CD.
But that's late 20th century technology, likely not appealing to
the cited customer.


You are right. I just meant the simplest way to upload the files from CD 
to mainframe DASD. I really cannot imagine a mainframe shop without any 
PC. It just cannot be true! 


BTW: I used to work as a consultant (read: in other datacenters), 
sometimes I met very strange troubles with very simple things. In fact 
it is usually much harder to read data from the tape than upload data 
from CD. Of course using IND$FILE, ftp is oftenly to modern. 

However reading from CD is usually simpler *from procedural point of view*.

Regards
--
Radoslaw Skorupka
Lodz, Poland


--
BRE Bank SA
ul. Senatorska 18
00-950 Warszawa
www.brebank.pl

Sąd Rejonowy dla m. st. Warszawy 
XII Wydział Gospodarczy Krajowego Rejestru Sądowego, 
nr rejestru przedsiębiorców KRS 025237

NIP: 526-021-50-88
Według stanu na dzień 01.01.2009 r. kapitał zakładowy BRE Banku SA (w całości 
wpłacony) wynosi 118.763.528 złotych. W związku z realizacją warunkowego 
podwyższenia kapitału zakładowego, na podstawie uchwały XXI WZ z dnia 16 marca 
2008r., oraz uchwały XVI NWZ z dnia 27 października 2008r., może ulec 
podwyższeniu do kwoty 123.763.528 zł. Akcje w podwyższonym kapitale zakładowym 
BRE Banku SA będą w całości opłacone.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: How to use CSI Catalog Search Interface

2009-03-06 Thread Gilbert Saint-Flour

Lizette,

File 183 of the CBT tape contains two REXX execs (called XDELETE and XRENAME) 
which use IGGCSI00 to retrieve VSAM and non-VSAM info.
They're both available here :   http://gsf-soft.com/Freeware/

XDELETE was published on TSO-REXX in 1998 - you'll find it here : 
http://www.google.com/search?&q=iggcsi00+xdelete

-- 
 Gilbert Saint-Flour
 GSF Software
 http://gsf-soft.com/

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

"Media manager" is the future?

2009-03-06 Thread John McKown

Or perhaps whatever has/will replace it? The reason that I ask is that it
seems that while DFSMSdfp clings tenaciously to the 3390 DASD architecture,
it is also using this interface (with 4K physical blocks) for all new I/O.
IIRC, it was first just a part of VSAM. I am not sure, but I'd bet that
PDS/E and HFS use it as well. Is this the "master plan" so that all access
methods will eventually use this one interface? I could go with that if it
meant that eventually non-3390 DASD architectures (such as SCSI/SAN) were
supported.

Just Friday musings. Brought on by my dislike of zFS being based on LDS data
sets. Because what I recently needed was a really huge (10 x 3390-3) UNIX
filesystem. Which meant a new storage class & storage group for segregation
from other data. In the past (non-VSAM, non-HFS), I could just grab some
"free" volumes and create a multi-volume dataset on them. Not any more. What
a bother.

--
John

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: "Media manager" is the future?

2009-03-06 Thread Daniel McLaughlin

LDS? What do the Mormons have to do with this? Are they encroaching on 
storage now?

Back to Friday musings

Daniel McLaughlin
Z-Series Systems Programmer
Information & Communications Technology
Crawford & Company
4680 N. Royal Atlanta
Tucker GA 30084 
phone: 770-621-3256 
fax: 770-621-3237
cell: 770-666-7969
email: daniel_mclaugh...@us.crawco.com
web: www.crawfordandcompany.com 





John McKown  
Sent by: IBM Mainframe Discussion List 
03/06/2009 12:44 PM
Please respond to
IBM Mainframe Discussion List 


To
IBM-MAIN@bama.ua.edu
cc

Subject
"Media manager" is the future?






-- Information from the mail header 
---
Sender:   IBM Mainframe Discussion List 
Poster:   John McKown 
Subject:  "Media manager" is the future?
---

Or perhaps whatever has/will replace it? The reason that I ask is that it
seems that while DFSMSdfp clings tenaciously to the 3390 DASD 
architecture,
it is also using this interface (with 4K physical blocks) for all new I/O.
IIRC, it was first just a part of VSAM. I am not sure, but I'd bet that
PDS/E and HFS use it as well. Is this the "master plan" so that all access
methods will eventually use this one interface? I could go with that if it
meant that eventually non-3390 DASD architectures (such as SCSI/SAN) were
supported.

Just Friday musings. Brought on by my dislike of zFS being based on LDS 
data
sets. Because what I recently needed was a really huge (10 x 3390-3) UNIX
filesystem. Which meant a new storage class & storage group for 
segregation
from other data. In the past (non-VSAM, non-HFS), I could just grab some
"free" volumes and create a multi-volume dataset on them. Not any more. 
What
a bother.

--
John

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html




Consider the environment before printing this message.

This transmission is intended exclusively for the individual or entity to which 
it is addressed. This communication may contain information that is 
confidential, proprietary, privileged or otherwise exempt from disclosure. If 
you are not the named addressee, you are NOT authorized to read, print, retain, 
copy or disseminate this communication, its attachments or any part of them. If 
you have received this communication in error, please notify the sender 
immediately and delete this communication from all computers.  This 
communication does not form any contractual obligation on behalf of the sender, 
the sender's employer, or the employer's parent company, affiliates or 
subsidiaries.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: [TSO-REXX] How to use CSI Catalog Search Interface

2009-03-06 Thread Lizette Koehler

Thanks to Dr. Michael Ebert from the DB2 world, I have a good example of what I 
am trying to do with CSI.  His code is located on www.idug.org.

His process combines CSI REXX with SAS to produce a nice report.  I will use 
that as a base and continue from there.

The modifications I had been making are on the right track. I just have to work 
harder at breaking down the WORKAREA where the information is returned.

Thanks to all who offered me code and advice.

Lizette

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking


---
Is there any RACF password rule that can validate the password cannot be 
a part of USERID? or only write a user exit to implement it?

-
I used an exit to prevent the password from being a ANAGRAM (scramble) 
of the userid. I used the USERIDS to fill in a translate table with 
non-zero values for each character of the USERID. Then I did a TRT on 
the password using that table. If the TRT completed, I rejected the 
password. I also used this exit to require that passwords could not 
start or end with a single numeric digit and enforced a minimum length 
of 6 characters. You can basically implement any rules you like using 
the password validation exit, and the code isn't really all that 
difficult. If I can find it, I'll send you a copy of my exit's source 
code, privately.


--
Rick
--
Remember that if you’re not the lead dog, the view never changes.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking



Yikes,

Should I be scared of this? Externalizing the password rules in REXX?

Seems to make it too easy to "collect" passwords.

You can always use RACF to prevent anyone reading the REXX dataset. ;-)

--
Rick
--
Remember that if you’re not the lead dog, the view never changes.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking


---
IMHO: exits as a subspecies are evil critters. They become an ongoing 
maintenance challenge and tend to attract unwelcome attention from 
auditors. Exits are hard to write, hard to stress test, and introduce a 
level of risk. You need extraordinary measures in place to protect the 
code.

--

I disagree, Hal. Exits CAN be overused and poorly coded; no argument 
there. But they often provide the only mechanism of tayloring function 
to fit business or technical needs, or sometimes arbitrary mandates from 
senior management. Testing a new installation or upgraded level of the 
OS need not be excessively delayed by the presence of exits; you just 
need to have good, solid code and a good testing methodology in place. 
But you need that anyway, don't you? As far as auditors are concerned, 
if they know what they're actually auditing, then they will understand 
reasoned arguments in favor of the appropriate exit. And of course 
you're going to protect ANY exit as carefully, or more carefully, than 
any other piece of APF-authorized code. Right?


--
Rick
--
Remember that if you’re not the lead dog, the view never changes.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Tony B.

Exits are a good alternative when:  1. The skillful author never retires,
finds a better job, gets laid off, is transferred, gets fired, wins the
lottery, or ages.  2. The company never is merged, acquired, downsizes, asks
for a government bailout, acquires another RACF company. 3. The source is
never misplaced. 4. zOS is never upgraded from OS390, MVS/ESA, MVS-prior
flavors.

Else, the term exit should be renamed to "future headache for its
inheritors."  5% of my experiences involved exits where the original author
was still available...

Jaded.  :-(




-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Rick Fochtman
Sent: Friday, March 06, 2009 12:34 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

--
-
IMHO: exits as a subspecies are evil critters. They become an ongoing
maintenance challenge and tend to attract unwelcome attention from auditors.
Exits are hard to write, hard to stress test, and introduce a level of risk.
You need extraordinary measures in place to protect the code.

--

I disagree, Hal. Exits CAN be overused and poorly coded; no argument there.
But they often provide the only mechanism of tayloring function to fit
business or technical needs, or sometimes arbitrary mandates from senior
management. Testing a new installation or upgraded level of the OS need not
be excessively delayed by the presence of exits; you just need to have good,
solid code and a good testing methodology in place. 
But you need that anyway, don't you? As far as auditors are concerned, if
they know what they're actually auditing, then they will understand reasoned
arguments in favor of the appropriate exit. And of course you're going to
protect ANY exit as carefully, or more carefully, than any other piece of
APF-authorized code. Right?

--
Rick
--
Remember that if you're not the lead dog, the view never changes.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.8/1985 - Release Date: 03/06/09
07:20:00

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Schwarz, Barry A

How do any of these "considerations" differ between an exit and the key
applications the business depends on and without which they wouldn't
need a computer system at all (or even be in business)?

-Original Message-
From: Tony B. 
Sent: Friday, March 06, 2009 10:55 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

Exits are a good alternative when:  1. The skillful author never
retires,
finds a better job, gets laid off, is transferred, gets fired, wins the
lottery, or ages.  2. The company never is merged, acquired, downsizes,
asks
for a government bailout, acquires another RACF company. 3. The source
is
never misplaced. 4. zOS is never upgraded from OS390, MVS/ESA, MVS-prior
flavors.

Else, the term exit should be renamed to "future headache for its
inheritors."  5% of my experiences involved exits where the original
author
was still available...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Tony B.

'cuz the RACF ones I have to deal with...  :-) 

-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Schwarz, Barry A
Sent: Friday, March 06, 2009 1:09 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

How do any of these "considerations" differ between an exit and the key
applications the business depends on and without which they wouldn't need a
computer system at all (or even be in business)?

-Original Message-
From: Tony B. 
Sent: Friday, March 06, 2009 10:55 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

Exits are a good alternative when:  1. The skillful author never retires,
finds a better job, gets laid off, is transferred, gets fired, wins the
lottery, or ages.  2. The company never is merged, acquired, downsizes, asks
for a government bailout, acquires another RACF company. 3. The source is
never misplaced. 4. zOS is never upgraded from OS390, MVS/ESA, MVS-prior
flavors.

Else, the term exit should be renamed to "future headache for its
inheritors."  5% of my experiences involved exits where the original author
was still available...

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.8/1985 - Release Date: 03/06/09
07:20:00

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF p assword & id checkin g‏

2009-03-06 Thread john gilmore

Tony B's strictures, which begin

| Exits are a good alternative when: 1. The skillful author

| never retires, finds a better job, gets laid off, is

| transferred, gets fired, wins the lottery, or ages.

| 2. . . .

are apposite; and it is easy to sympathize with the bad experiences they
reflect.

They are also generic. They are equally applicable to user-written SVC
routines [discussed in chapter 23 immediately following chapter 22, Exit
routines, in the z/OS MVS Authoriized Assembler Services Guide] and to much
else.

I spent most of yesterday replacing an old SVC, which was written by perhaps
the 213th sharpest knife in the drawer, with some PC routines; and if I needed
a litany about the quality of that SVC I could quote Tony on exits.

Bad code is ubiquitous for a variety of familiar reasons, and I doubt that
avoiding exits because they are often written badly and/or documented poorly
would be helpful.

Its effects will be like those of the usual American traffic engineer's no left
turns sign: it will serve only to move the problem to another location.

John Gilmore Ashland, MA 01721-1817 USA

_
Windows Live™ Contacts: Organize your contact list.
http://windowslive.com/connect/post/marcusatmicrosoft.spaces.live.com-Blog-cns!503D1D86EBB2B53C!2285.entry?ocid=TXT_TAGLM_WL_UGC_Contacts_032009

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: How to use CSI Catalog Search Interface

2009-03-06 Thread Kirk Wolf

The z/OS Java SDK - JZOS toolkit contains a nice wrapper for IGGCSI00 and
also an api for reading DSCBs.   There are sample programs available (see
IBM link below).

We also plan on releasing an update to the JZOS Cookbook which contains a
z/OS Java web service to using IGGCSI00, and a sample rich web 2.0 UI that
uses web service.

Kirk Wolf
Dovetailed Technologies

http://dovetail.com

IBM JZOS home page:
http://www.ibm.com/servers/eserver/zseries/software/java/products/jzos/overview.html

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking‏

2009-03-06 Thread Ted MacNEIL

>Bad code is ubiquitous for a variety of familiar reasons, and I doubt that 
>avoiding exits because they are often written badly and/or documented poorly 
>would be helpful.  

I agree, for many reasons.
Bad code abounds.
If we used Tony's strictures, then we would never write system of application 
code.

The problem is code has to be written, so we have to live with it.

The other problem is, even well-written code has a problem if the writer's 
successor doesn't understand the language, or the intent, of the code.

-
Too busy driving to stop for gas!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

GET IBM-MAIN INFO

2009-03-06 Thread Richard Pace

-- 
Regards,
Richard
rpace.org

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Isn't today Mantissa day?

2009-03-06 Thread David Andrews

Who's still hasn't left Austin who can say what z/VOS is?  The Mantissa
website only says "Yep, we announced it in Austin".

-- 
David Andrews
A. Duda and Sons, Inc.
david.andr...@duda.com

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Roach, Dennis (N-GHG)

Look at http://www.mantissa.com/SHARE-conference 

Windows under VM on a z

Dennis Roach
GHG Corporation
Lockheed Martin Mission Services
Flight Design and Operations Contract
Address:
   2100 Space Park Drive 
   LM-15-4BH
   Houston, Texas 77058
Mail:
   P.O. Box 58487
   Mail Code H4C
   Houston, Texas 77258
Phone:
   Voice:  (281)336-5027
   Cell:   (713)591-1059
   Fax:(281)336-5410
E-Mail:  dennis.ro...@lmco.com

All opinions expressed by me are mine and may not agree with my employer
or any person, company, or thing, living or dead, on or near this or any
other planet, moon, asteroid, or other spatial object, natural or
manufactured, since the beginning of time.

> -Original Message-
> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of David Andrews
> Sent: Friday, March 06, 2009 2:06 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Isn't today Mantissa day?
> 
> Who's still hasn't left Austin who can say what z/VOS is?  The
Mantissa
> website only says "Yep, we announced it in Austin".
> 
> --
> David Andrews
> A. Duda and Sons, Inc.
> david.andr...@duda.com
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Lionel B Dyck

If you do a google search for mantissa and z/vos you will get a number of 
hits - nothing concrete as yet that I can see. 

Hopefully we'll get more after todays announcement at SHARE

Lionel B. Dyck, Consultant/Specialist 
Enterprise Platform Services, Mainframe Engineering 
KP-IT Enterprise Engineering 
925-926-5332 (8-473-5332) | E-Mail: lionel.b.d...@kp.org 
AIM: lbdyck | Yahoo IM: lbdyck 
Kaiser Service Credo: "Our cause is health. Our passion is service. We?re 
here to make lives better.? 

?Never attribute to malice what can be caused by miscommunication.? 

NOTICE TO RECIPIENT: If you are not the intended recipient of this e-mail, 
you are prohibited from sharing, copying, or otherwise using or disclosing 
its contents. If you have received this e-mail in error, please notify the 
sender immediately by reply e-mail and permanently delete this e-mail and 
any attachments without reading, forwarding or saving them. Thank you. 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

IDC3009i RC48 RSN142 with ALTER TODATE(...)

2009-03-06 Thread John Kelly

I was trying remove date expiration for some non-VSAM SMS DSNs. 

Cmd: ALTERT DSN TODATE(2009065) I know that the date can not be any 
earlier than the current day.

On two of three systems I get RC48 RSN142 which says
"An ALTER fails due to unsuccessful DADSM UPDATE function". 
I can't figure out how to reconcile the RSN148 to the DADSM UPDATE four 
byte reason code and the message explanation doesn't help too much. The 
DSNs are shared between systems and are in a common UCAT. The OS is 1.4 
though.



Jack Kelly
202-502-2390 (Office)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Ken Porowski

>From Mantissas web site

UPDATE: Just want to thank everyone who was in attendance for the SHARE
presentation. So...Now that the concept has officially been laid bare,
we plan on publishing a development blog as a means of keeping you
informed of the progress being made on zVos. That's coming shortly. In
the meantime, thank you again for your time and interest. If you have
any questions or comments, we sincerely welcome the dialogue...
 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Rich Smrcina

Strictly speaking it's x86 architecture execution under z/VM.  If you decide to use 
Windows that you're choice.  Saying x86 is Windows is like saying System z is z/OS.


Roach, Dennis (N-GHG) wrote:
Look at http://www.mantissa.com/SHARE-conference 


Windows under VM on a z

Dennis Roach
GHG Corporation
Lockheed Martin Mission Services
Flight Design and Operations Contract
Address:
   2100 Space Park Drive 
   LM-15-4BH

   Houston, Texas 77058
Mail:
   P.O. Box 58487
   Mail Code H4C
   Houston, Texas 77258
Phone:
   Voice:  (281)336-5027
   Cell:   (713)591-1059
   Fax:(281)336-5410
E-Mail:  dennis.ro...@lmco.com


--
Rich Smrcina
VM Assist, Inc.
Phone: 414-491-6001
Ans Service:  360-715-2467
http://www.linkedin.com/in/richsmrcina

Catch the WAVV!  http://www.wavv.org
WAVV 2009 - Orlando, FL - May 15-19, 2009

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Chase, John

> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Roach, Dennis (N-GHG)
> 
> Look at http://www.mantissa.com/SHARE-conference

I see nothing new there, beyond "We announced it".

> Windows under VM on a z

Saw nothing about that, either.

   -jc-

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: IDC3009i RC48 RSN142 with ALTER TODATE(...)

2009-03-06 Thread Neal Scheffler


I use

ALTER dsn NULL(RETENTION)

Neal Scheffler

John Kelly wrote:
I was trying remove date expiration for some non-VSAM SMS DSNs. 

Cmd: ALTERT DSN TODATE(2009065) I know that the date can not be any 
earlier than the current day.


On two of three systems I get RC48 RSN142 which says
"An ALTER fails due to unsuccessful DADSM UPDATE function". 
I can't figure out how to reconcile the RSN148 to the DADSM UPDATE four 
byte reason code and the message explanation doesn't help too much. The 
DSNs are shared between systems and are in a common UCAT. The OS is 1.4 
though.





Jack Kelly
202-502-2390 (Office)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread J R

> I see nothing new there, beyond "We announced it".

 

 

I see nothing there at all!  The website seems to have issues.  

Many links result in a blank screen.  Very frustrating!  

 

 

> Date: Fri, 6 Mar 2009 14:27:58 -0600

> From: jch...@ussco.com

> Subject: Re: Isn't today Mantissa day?

> To: IBM-MAIN@bama.ua.edu

> 

> > -Original Message-

> > From: IBM Mainframe Discussion List On Behalf Of Roach, Dennis (N-GHG)

> > 

> > Look at http://www.mantissa.com/SHARE-conference

> 

> I see nothing new there, beyond "We announced it".

> 

> > Windows under VM on a z

> 

> Saw nothing about that, either.

> 

> -jc-

 

 

 

_
Express your personality in color! Preview and select themes for Hotmail®. 
http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

Now you need to talk about documentqation. It's like sex. When it's bad, 
it's still better than nothing and when it's good, it's really great.


Tony B. wrote:


Exits are a good alternative when:  1. The skillful author never retires,
finds a better job, gets laid off, is transferred, gets fired, wins the
lottery, or ages.  2. The company never is merged, acquired, downsizes, asks
for a government bailout, acquires another RACF company. 3. The source is
never misplaced. 4. zOS is never upgraded from OS390, MVS/ESA, MVS-prior
flavors.

Else, the term exit should be renamed to "future headache for its
inheritors."  5% of my experiences involved exits where the original author
was still available...

Jaded.  :-(


   


-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf
Of Rick Fochtman
Sent: Friday, March 06, 2009 12:34 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

--
-
IMHO: exits as a subspecies are evil critters. They become an ongoing
maintenance challenge and tend to attract unwelcome attention from auditors.
Exits are hard to write, hard to stress test, and introduce a level of risk.
You need extraordinary measures in place to protect the code.

--

I disagree, Hal. Exits CAN be overused and poorly coded; no argument there.
But they often provide the only mechanism of tayloring function to fit
business or technical needs, or sometimes arbitrary mandates from senior
management. Testing a new installation or upgraded level of the OS need not
be excessively delayed by the presence of exits; you just need to have good,
solid code and a good testing methodology in place. 
But you need that anyway, don't you? As far as auditors are concerned, if

they know what they're actually auditing, then they will understand reasoned
arguments in favor of the appropriate exit. And of course you're going to
protect ANY exit as carefully, or more carefully, than any other piece of
APF-authorized code. Right?

--
Rick
--
Remember that if you're not the lead dog, the view never changes.

--
For IBM-MAIN subscribe / signoff / archive access instructions, send email
to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the
archives at http://bama.ua.edu/archives/ibm-main.html
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.11.8/1985 - Release Date: 03/06/09
07:20:00

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

 



--
Rick
--
Remember that if you’re not the lead dog, the view never changes.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Roach, Dennis (N-GHG)

The abstract

Over the last decade IBM has quietly opened a world of virtualization
possibilities through changes in the System z instruction set and
advances in their chip technology. These changes have made possible x86
virtualization alternatives never imagined. 

Find out how you can leverage System z to achieve x86 virtualization
goals faster and more cost effectively than you ever thought possible. 

Learn how you can deploy and manage native x86 Windows(r) and Linux
images under z/VM. <--<<<

Gain an understanding of how you can simplify operations and more easily
reach virtualization and cost containment goals through:

JIT deployment of virtualized x86 OS images 
Reductions in deployment costs 
Simplified image and deployment maintenance 
Reduced power and space requirements 

Learn more about z/VOS, the system that makes this virtualization
alternative possible. Gain first-hand knowledge of:

How the technology works 
the meaning of Single Pass Virtualization (SPV) 
x86 network, file system and GUI considerations 
z/VM service machine considerations 
Guest x86 machine IPL, clone, checkpoint capabilities 
z/VOS administration   

Dennis Roach
GHG Corporation
Lockheed Martin Mission Services
Flight Design and Operations Contract
Address:
   2100 Space Park Drive 
   LM-15-4BH
   Houston, Texas 77058
Mail:
   P.O. Box 58487
   Mail Code H4C
   Houston, Texas 77258
Phone:
   Voice:  (281)336-5027
   Cell:   (713)591-1059
   Fax:(281)336-5410
E-Mail:  dennis.ro...@lmco.com

All opinions expressed by me are mine and may not agree with my employer
or any person, company, or thing, living or dead, on or near this or any
other planet, moon, asteroid, or other spatial object, natural or
manufactured, since the beginning of time.

> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of J R
> Sent: Friday, March 06, 2009 2:36 PM
> > I see nothing new there, beyond "We announced it".
> I see nothing there at all!  The website seems to have issues.
> Many links result in a blank screen.  Very frustrating!

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Ed Finnell

 
In a message dated 3/6/2009 2:33:21 P.M. Central Standard Time,  
d...@lists.duda.com writes:

The Mantissa
website only says "Yep, we announced it in  Austin".


>>
maybe it's a new form of snubbery. If anybody  needs any I've got about 300 
ibm-main Austin stickers that nobody claimed...so  sad-maybe it's the economy.




**A Good Credit Score is 700 or Above. See yours in just 2 easy 
steps! 
(http://pr.atwola.com/promoclk/100126575x1219957551x1201325337/aol?redir=http:%2F%2Fwww.freecreditreport.com%2Fpm%2Fdefault.aspx%3Fsc%3D668072%26hmpgID
%3D62%26bcd%3DfebemailfooterNO62)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Hal Merritt

In my 40+ years, exits tend to be politically motivated. That is, the 
business/technical issue is really easily solvable some other way. 

For the case in point, someone just wants the system to work differently. There 
is no technical justification, no business justification, and arguable security 
grounds. 

Of course, there are a few exists that make perfect business/technical sense. 
But the fewer the better. And certainly never, ever, to satisfy an audit 
requirement.   

Just my $0.02   



-Original Message-
From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On Behalf Of 
Schwarz, Barry A
Sent: Friday, March 06, 2009 1:09 PM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

How do any of these "considerations" differ between an exit and the key
applications the business depends on and without which they wouldn't
need a computer system at all (or even be in business)?

-Original Message-
From: Tony B. 
Sent: Friday, March 06, 2009 10:55 AM
To: IBM-MAIN@bama.ua.edu
Subject: Re: RACF password & id checking

Exits are a good alternative when:  1. The skillful author never
retires,
finds a better job, gets laid off, is transferred, gets fired, wins the
lottery, or ages.  2. The company never is merged, acquired, downsizes,
asks
for a government bailout, acquires another RACF company. 3. The source
is
never misplaced. 4. zOS is never upgraded from OS390, MVS/ESA, MVS-prior
flavors.

Else, the term exit should be renamed to "future headache for its
inheritors."  5% of my experiences involved exits where the original
author
was still available...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
NOTICE: This electronic mail message and any files transmitted with it are 
intended
exclusively for the individual or entity to which it is addressed. The message, 
together with any attachment, may contain confidential and/or privileged 
information.
Any unauthorized review, use, printing, saving, copying, disclosure or 
distribution 
is strictly prohibited. If you have received this message in error, please 
immediately advise the sender by reply email and delete all copies.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Dave Salt

So if IBM is making it possible to run Windows on Z, does this mean they won't 
object if people start running Z on Windows?;-)

Dave Salt

SimpList(tm) - try it; you'll get it!   
http://www.mackinney.com/products/SIM/simplist.htm   
  



 
> Date: Fri, 6 Mar 2009 13:41:39 -0700
> From: dennis.ro...@lmco.com
> Subject: Re: Isn't today Mantissa day?
> To: IBM-MAIN@bama.ua.edu
> 
> The abstract
> 
> Over the last decade IBM has quietly opened a world of virtualization
> possibilities through changes in the System z instruction set and
> advances in their chip technology. These changes have made possible x86
> virtualization alternatives never imagined. 
> 
> Find out how you can leverage System z to achieve x86 virtualization
> goals faster and more cost effectively than you ever thought possible. 
> 
> Learn how you can deploy and manage native x86 Windows(r) and Linux
> images under z/VM. <--<<<
> 
> Gain an understanding of how you can simplify operations and more easily
> reach virtualization and cost containment goals through:
> 
> JIT deployment of virtualized x86 OS images 
> Reductions in deployment costs 
> Simplified image and deployment maintenance 
> Reduced power and space requirements 
> 
> Learn more about z/VOS, the system that makes this virtualization
> alternative possible. Gain first-hand knowledge of:
> 
> How the technology works 
> the meaning of Single Pass Virtualization (SPV) 
> x86 network, file system and GUI considerations 
> z/VM service machine considerations 
> Guest x86 machine IPL, clone, checkpoint capabilities 
> z/VOS administration 
> 
> Dennis Roach
> GHG Corporation
> Lockheed Martin Mission Services
> Flight Design and Operations Contract
> Address:
> 2100 Space Park Drive 
> LM-15-4BH
> Houston, Texas 77058
> Mail:
> P.O. Box 58487
> Mail Code H4C
> Houston, Texas 77258
> Phone:
> Voice: (281)336-5027
> Cell: (713)591-1059
> Fax: (281)336-5410
> E-Mail: dennis.ro...@lmco.com
> 
> All opinions expressed by me are mine and may not agree with my employer
> or any person, company, or thing, living or dead, on or near this or any
> other planet, moon, asteroid, or other spatial object, natural or
> manufactured, since the beginning of time.
> 
> > From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> > Behalf Of J R
> > Sent: Friday, March 06, 2009 2:36 PM
> > > I see nothing new there, beyond "We announced it".
> > I see nothing there at all! The website seems to have issues.
> > Many links result in a blank screen. Very frustrating!
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html

_
Chat with the whole group, and bring everyone together.
http://go.microsoft.com/?linkid=9650735
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Roach, Dennis (N-GHG)

I have had to do exactly what is being discussed in z/OS and Linux. 

When you are a government contractor and the Inspector General's office
says do it or the certification for the facility 
is canceled (along with your contract), you need no more business
justification.

As or security justification, all of the OIG requirements in this area
are industry recognized best practices.

Dennis Roach
GHG Corporation
Lockheed Martin Mission Services
Flight Design and Operations Contract
Address:
   2100 Space Park Drive 
   LM-15-4BH
   Houston, Texas 77058
Mail:
   P.O. Box 58487
   Mail Code H4C
   Houston, Texas 77258
Phone:
   Voice:  (281)336-5027
   Cell:   (713)591-1059
   Fax:(281)336-5410
E-Mail:  dennis.ro...@lmco.com

All opinions expressed by me are mine and may not agree with my employer
or any person, company, or thing, living or dead, on or near this or any
other planet, moon, asteroid, or other spatial object, natural or
manufactured, since the beginning of time.


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of Hal Merritt
> Sent: Friday, March 06, 2009 3:09 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: RACF password & id checking
> 
> In my 40+ years, exits tend to be politically motivated. That is, the
> business/technical issue is really easily solvable some other way.
> 
> For the case in point, someone just wants the system to work
> differently. There is no technical justification, no business
> justification, and arguable security grounds.
> 
> Of course, there are a few exists that make perfect business/technical
> sense. But the fewer the better. And certainly never, ever, to satisfy
> an audit requirement.
> 
> Just my $0.02
> 
> 
> 
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:ibm-m...@bama.ua.edu] On
> Behalf Of Schwarz, Barry A
> Sent: Friday, March 06, 2009 1:09 PM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: RACF password & id checking
> 
> How do any of these "considerations" differ between an exit and the
key
> applications the business depends on and without which they wouldn't
> need a computer system at all (or even be in business)?
> 
> -Original Message-
> From: Tony B.
> Sent: Friday, March 06, 2009 10:55 AM
> To: IBM-MAIN@bama.ua.edu
> Subject: Re: RACF password & id checking
> 
> Exits are a good alternative when:  1. The skillful author never
> retires,
> finds a better job, gets laid off, is transferred, gets fired, wins
the
> lottery, or ages.  2. The company never is merged, acquired,
downsizes,
> asks
> for a government bailout, acquires another RACF company. 3. The source
> is
> never misplaced. 4. zOS is never upgraded from OS390, MVS/ESA, MVS-
> prior
> flavors.
> 
> Else, the term exit should be renamed to "future headache for its
> inheritors."  5% of my experiences involved exits where the original
> author
> was still available...
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
> Search the archives at http://bama.ua.edu/archives/ibm-main.html
> NOTICE: This electronic mail message and any files transmitted with it
> are intended
> exclusively for the individual or entity to which it is addressed. The
> message,
> together with any attachment, may contain confidential and/or
> privileged information.
> Any unauthorized review, use, printing, saving, copying, disclosure or
> distribution
> is strictly prohibited. If you have received this message in error,
> please
> immediately advise the sender by reply email and delete all copies.
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Ken Porowski

IBM isn't making it possible, Mantissa is. 

-Original Message-
Dave Salt

So if IBM is making it possible to run Windows on Z, does this mean they
won't object if people start running Z on Windows?;-)

Dave Salt

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: Isn't today Mantissa day?

2009-03-06 Thread Paul Gilmartin

On Fri, 6 Mar 2009 16:19:46 -0500, Dave Salt wrote:

>So if IBM is making it possible to run Windows on Z, does this mean they won't 
>object if people start running Z on Windows?;-)
>
No, it means Intel won't object.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: "Media manager" is the future?

On Fri, 6 Mar 2009 11:44:11 -0600, John McKown  wrote:
>I am not sure, but I'd bet that
>PDS/E and HFS use it as well. 

They do.  


>
>Just Friday musings. Brought on by my dislike of zFS being based on LDS data
>sets. Because what I recently needed was a really huge (10 x 3390-3) UNIX
>filesystem. Which meant a new storage class & storage group for segregation
>from other data. In the past (non-VSAM, non-HFS), I could just grab some
>"free" volumes and create a multi-volume dataset on them. Not any more. What
>a bother.
>

Multi-volume HFS needs to be SMS managed also. So zFS is no different
in that respect.

Mark
--
Mark Zelden
Sr. Software and Systems Architect - z/OS Team Lead
Zurich North America / Farmers Insurance Group - ZFUS G-ITO
mailto:mark.zel...@zurichna.com
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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: "Media manager" is the future?

2009-03-06 Thread Bobbie Jo


" what I recently needed was a really huge (10 x 3390-3) UNIX

filesystem.".


okay, we have one zFS filesystem for downloads that is on a mod 54.



- Original Message - 
From: "John McKown" 

Newsgroups: bit.listserv.ibm-main
To: 
Sent: Friday, March 06, 2009 12:44 PM
Subject: "Media manager" is the future?



Or perhaps whatever has/will replace it? The reason that I ask is that it
seems that while DFSMSdfp clings tenaciously to the 3390 DASD 
architecture,

it is also using this interface (with 4K physical blocks) for all new I/O.
IIRC, it was first just a part of VSAM. I am not sure, but I'd bet that
PDS/E and HFS use it as well. Is this the "master plan" so that all access
methods will eventually use this one interface? I could go with that if it
meant that eventually non-3390 DASD architectures (such as SCSI/SAN) were
supported.

Just Friday musings. Brought on by my dislike of zFS being based on LDS 
data

sets. Because what I recently needed was a really huge (10 x 3390-3) UNIX
filesystem. Which meant a new storage class & storage group for 
segregation

from other data. In the past (non-VSAM, non-HFS), I could just grab some
"free" volumes and create a multi-volume dataset on them. Not any more. 
What

a bother.

--
John

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Use of the z/OS CMDS ABEND command

2009-03-06 Thread W. Kevin Kelley

We would very much appreciate hearing from customers that have used the 
z/OS CMDS ABEND command to terminate a command.

-- What commands have you terminated, and what was your experience in 
doing so? Was it worth the risk? Were there undesirable side-effects?

We are contemplating some changes in the behavior of CMDS ABEND to better 
protect the system from the termination of certain commands (for example, 
the termination of a command that can remove serialization and leave a 
resource vulnerable to inadvertent destruction). As a short term solution, we 
are thinking of establishing a list of commands that cannot be terminated 
because of the harm that termination can cause. We understand that this 
may reduce some of the usefulness of the CMDS ABEND command in certain 
situations. We would eventually like to have more granularity through a 
service by which a command can indicate when it can be terminated and 
when it cannot, the intention being that small, critical sections of the 
command could be protected from termination while other sections of the 
command would allow termination.

Clearly, we would not contemplate these kinds of changes unless we felt there 
was a problem, but we'd like to hear from you before we proceed.

W. Kevin Kelley  IBM POK Lab -- z/OS Core Technology Development

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

C Novice


I'm a novice trying to get a simple C program running under MVS.

I'm attempting to get file output to
//OUTF DD SYSOUT=A
with the following program.

#include 
int main(void)
{
  FILE *outf = NULL;
  printf("TESTFILE has been entered.\n");
  outf = fopen("dd:OUTF","recfm=fba, w+");
  if (!outf)
{
printf("fopen error on FILE *outf.\n");
return 4;
}
  fprintf(outf, "outf open ...\n");
  fclose(outf);
  return 0;
}

So far, with many variations to the fopen string, I get only the 
following output on SYSPRINT, no output to OUTF.


TESTFILE has been entered.
fopen error on FILE *outf.

Can anyone give me some advice on how to code this correctly ?

Regards

Lorne Dudley
Queen's University
Kingston, Ontario

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: RACF password & id checking

2009-03-06 Thread Tommy Tsui

I check the following web site and it shows z/os R9 that already
support this REXX...
http://www-03.ibm.com/servers/eserver/zseries/zos/racf/downloads/rexxpwexit.html

On Sat, Mar 7, 2009 at 12:50 AM, Walt Farrell  wrote:
> On Sat, 7 Mar 2009 00:12:16 +0800, Tommy Tsui  wrote:
>
>>I saw the REXX code and it's quite simple. Just turn it on...I will try it ..
>>thanks all of your help
>
> Do remember that it works only on z/OS R10 and later, though.
>
> --
>  Walt Farrell, CISSP
>  IBM STSM, z/OS Security Design
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

IPCS dump

2009-03-06 Thread Fred Hoffman

Hi Y'all,
 
I hate this as I just read  about the passing of the person that was the 
creator/teacher/guru regarding IPCS.
 
I just received a dump that I assume is in IPCS format and I don't have a clue, 
well a little, how to process this.
Is there anywhere I can find out the job stream etc. for the analysis on ths 
dataset.  It's been a long time since working with ZOS dumps, as I'm working in 
the VSE world now.  I need to find out what the dd name for input is and maybe 
some options for the dump analysis.  It's supposedy a loop, and I wrote the 
programs for the
most part so I'm not totally in the dark, but/. If someone could help me 
with this, I would be very grateful.
 
TIA,
 
Fred Hoffman

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: IPCS dump

2009-03-06 Thread Shane

On Fri, 2009-03-06 at 20:48 -0600, Fred Hoffman wrote:
>  
> Is there anywhere I can find out the job stream etc. for the analysis
> on ths dataset.

Fred, the IPCS manuals are online - here's a search for the 2.10 ones
(sorry about wrap);
http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/Shelves/EZ2ZO10L?filter=ipcs&SUBMIT=Search+titles

The User guide would be a good place to start - Ch 8 for batch.

Shane ...

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: C Novice

2009-03-06 Thread Bill Godfrey

On Fri, 6 Mar 2009 21:29:17 -0500, Lorne Dudley wrote:

>I'm a novice trying to get a simple C program running under MVS.
>
>I'm attempting to get file output to
>//OUTF DD SYSOUT=A
>with the following program.
>
>#include 
>int main(void)
>{
>   FILE *outf = NULL;
>   printf("TESTFILE has been entered.\n");
>   outf = fopen("dd:OUTF","recfm=fba, w+");
>   if (!outf)
> {

   perror("dd:OUTF");

> printf("fopen error on FILE *outf.\n");
> return 4;
> }
>   fprintf(outf, "outf open ...\n");
>   fclose(outf);
>   return 0;
>}
>
>So far, with many variations to the fopen string, I get only the
>following output on SYSPRINT, no output to OUTF.
>
>TESTFILE has been entered.
>fopen error on FILE *outf.
>
>Can anyone give me some advice on how to code this correctly ?
>

The "perror" function might give you more information about why fopen is 
failing. See above.

Bill

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: C Novice


Thanks for the hint Bill.

That gives me
dd:OUTF: EDC5057I The open mode string was invalid. (errno2=0xC00B0022)

I'll chase that mesage and see what I can decipher.

Regards

Lorne

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: C Novice

Hi Bill (or any other C programmer) !

OK, perror("dd:OUTF"); gives me

EDC5057I The open mode string was invalid. Explanation: The mode string 
passed to the fopen()/freopen() function was found to have invalid 
keywords, combinations, or characters. For example, if you are opening a 
ddname, be sure the DISP= specified on the DD statement is compatible 
with the open mode you specified. Programmer response: Correct the mode 
string and reissue the fopen()/freopen().

I'm not much wiser with this explanation.

I know that if I use only
outf = fopen("dd:OUTF","w+");
and
//OUTF DD DISP=OLD,DSN=SYS2#.C.OUTF

the program executes properly with zero return code.
In this case the OUTF file is on disk with recfm=vb, lrecl=1028, 
blksize=6144.

So I'm still in the dark as to how to get this to write to SYSOUT=A.

Regards

Lorne

On Fri, 6 Mar 2009 21:29:17 -0500, Lorne Dudley wrote:

> >I'm a novice trying to get a simple C program running under MVS.
> >
> >I'm attempting to get file output to
> >//OUTF DD SYSOUT=A
> >with the following program.
> >
> >#include 
> >int main(void)
> >{
> >   FILE *outf = NULL;
> >   printf("TESTFILE has been entered.\n");
> >   outf = fopen("dd:OUTF","recfm=fba, w+");
> >   if (!outf)
> > {

   perror("dd:OUTF");

> > printf("fopen error on FILE *outf.\n");
> > return 4;
> > }
> >   fprintf(outf, "outf open ...\n");
> >   fclose(outf);
> >   return 0;
> >}
> >
> >So far, with many variations to the fopen string, I get only the
> >following output on SYSPRINT, no output to OUTF.
> >
> >TESTFILE has been entered.
> >fopen error on FILE *outf.
> >
> >Can anyone give me some advice on how to code this correctly ?
> >

The "perror" function might give you more information about why fopen is
failing. See above.

Bill

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: C Novice


Hi Bill !

Through trial and error and the use of perror("dd:OUTF"); I have 
determined that this syntax works as expected.


outf = fopen("dd:OUTF", "w");

Thanks for the lead.

Regards

Lorne


Bill Godfrey wrote:

On Fri, 6 Mar 2009 21:29:17 -0500, Lorne Dudley wrote:


I'm a novice trying to get a simple C program running under MVS.

I'm attempting to get file output to
//OUTF DD SYSOUT=A
with the following program.

#include 
int main(void)
{
  FILE *outf = NULL;
  printf("TESTFILE has been entered.\n");
  outf = fopen("dd:OUTF","recfm=fba, w+");
  if (!outf)
{


   perror("dd:OUTF");


printf("fopen error on FILE *outf.\n");
return 4;
}
  fprintf(outf, "outf open ...\n");
  fclose(outf);
  return 0;
}

So far, with many variations to the fopen string, I get only the
following output on SYSPRINT, no output to OUTF.

TESTFILE has been entered.
fopen error on FILE *outf.

Can anyone give me some advice on how to code this correctly ?



The "perror" function might give you more information about why fopen is 
failing. See above.


Bill




--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: C Novice

2009-03-06 Thread Bill Godfrey

In the 2nd argument of fopen, the keyword parameters come after the mode. 
Try it with just "w" or "w, recfm=fba".

Bill

On Fri, 6 Mar 2009 23:21:41 -0500, Lorne Dudley wrote:

>Hi Bill (or any other C programmer) !
>
>OK, perror("dd:OUTF"); gives me
>
>EDC5057I The open mode string was invalid. Explanation: The mode string
>passed to the fopen()/freopen() function was found to have invalid
>keywords, combinations, or characters. For example, if you are opening a
>ddname, be sure the DISP= specified on the DD statement is compatible
>with the open mode you specified. Programmer response: Correct the mode
>string and reissue the fopen()/freopen().
>
>I'm not much wiser with this explanation.
>
>I know that if I use only
>outf = fopen("dd:OUTF","w+");
>and
>//OUTF DD DISP=OLD,DSN=SYS2#.C.OUTF
>
>the program executes properly with zero return code.
>In this case the OUTF file is on disk with recfm=vb, lrecl=1028,
>blksize=6144.
>
>So I'm still in the dark as to how to get this to write to SYSOUT=A.
>
>Regards
>
>Lorne
>
>On Fri, 6 Mar 2009 21:29:17 -0500, Lorne Dudley wrote:
>
> > >I'm a novice trying to get a simple C program running under MVS.
> > >
> > >I'm attempting to get file output to
> > >//OUTF DD SYSOUT=A
> > >with the following program.
> > >
> > >#include 
> > >int main(void)
> > >{
> > >   FILE *outf = NULL;
> > >   printf("TESTFILE has been entered.\n");
> > >   outf = fopen("dd:OUTF","recfm=fba, w+");
> > >   if (!outf)
> > > {
>
>perror("dd:OUTF");
>
> > > printf("fopen error on FILE *outf.\n");
> > > return 4;
> > > }
> > >   fprintf(outf, "outf open ...\n");
> > >   fclose(outf);
> > >   return 0;
> > >}
> > >
> > >So far, with many variations to the fopen string, I get only the
> > >following output on SYSPRINT, no output to OUTF.
> > >
> > >TESTFILE has been entered.
> > >fopen error on FILE *outf.
> > >
> > >Can anyone give me some advice on how to code this correctly ?
> > >
>
>The "perror" function might give you more information about why fopen is
>failing. See above.
>
>Bill
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html

Re: C Novice