Re: No z/OS UNIX Support in System REXX?

2007-12-07 Thread Edward Jaffe

Edward Jaffe wrote:

IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00110
ICH408I JOB(AXR04   ) STEP(AXR04   ) CL(PROCESS )
 OMVS SEGMENT NOT DEFINED

Anyone got this to work?


Just heard back from IBM on this. Although stated in reverse, they have 
essentially confirmed the restriction Patrick O'Keefe found in the 
Assembler Services Guide (the first place I would think to look for 
information about System REXX).


Understand, this means System REXX execs cannot issue any command that 
directly or indirectly uses z/OS UNIX services. For example, the FTP 
command.



|Hello Edward.  Well I'm afraid the news isn't good.  System Rexx is
|not supported under Unix System Services host commands This is with
|either TSO=YES or TSO=NO.  This is described in the Auth Assembler
|Services manual under SYSTEM REXX.
|Let me know if you have any questions.


--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/

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


Re: No z/OS UNIX Support in System REXX?

2007-12-06 Thread Walt Farrell
On Thu, 6 Dec 2007 11:18:28 -0800, Edward Jaffe
<[EMAIL PROTECTED]> wrote:

>Thanks, Patrick! I looked all over the place for that "official"
>statement! I've had a PMR opened with IBM since yesterday and even they
>haven't even been able to tell me this yet!
>
>It appears that System REXX does not completely or properly propagate
>identity/security information to its "worker" TCBs or address spaces.
>Instead of leveraging the existing WLM services -- used by the likes of
>Websphere -- in its design, the System REXX developers decided to use a
>"roll your own" multi-address space server approach. This total lack of
>support for z/OS UNIX services looks to be an unfortunate outcome of
>that questionable decision. :-(

Identity propagation is a different question than not supporting REXX, Ed. 
That statement in the Authorized Assembler Services Guide simply means that
ADDRESS SYSCALL is not available.And the messages listed earlier in this
thread do mean, I think, what people said they meant, except for one
possibility.  An ICH408I with JOB/STEP means one of two things: Either
(a) the named job does not have a RACF identity defined; or
(b) it's a server, and it's processing a request on behalf of a client that
does not have a RACF identity defined.

Either of those might have happened from the info in this thread so far.

AXREXX does propagate basic info about the caller's identity, and that will
enable  basic UNIX identity processing, too.

Nothing except UNIX services (as far as I know) will propagate complete UNIX
identity info (Effective/Saved/Real UID, current supplemental groups), and
they only do that during fork() and spawn() processing, and some flavors of
AFUNIX domain socket operations.

I'm pretty sure the WLM services don't propagate all the UNIX identity info
either, and from what I remember they pass the same info as AXREXX does.

I'm not sure that simply providing ADDRESS SYSCALL would resolve all the
problems.  To allow UNIX processing in a server address space they also need
to worry about process and thread handling, dubbing and undubbing of the
threads or processes, etc. and I don't know if AXREXX has that support
either.  But that's also not related to whether they use WLM services or not.

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

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


Re: No z/OS UNIX Support in System REXX?

2007-12-06 Thread Edward Jaffe

Patrick O'Keefe wrote:

From
z/OS 1.9 MVS Programming: Authorized Assembler Services Guide
Chapter 31. System REXX

Neither the TSO=YES or TSO=NO environments support UNIX System 
Services host commands.


That doesn't exactly explain why the lack of support should result 
in that RACF error, but it sounds like you are out of luck.


Time for a requirement?
  


Thanks, Patrick! I looked all over the place for that "official" 
statement! I've had a PMR opened with IBM since yesterday and even they 
haven't even been able to tell me this yet!


It appears that System REXX does not completely or properly propagate 
identity/security information to its "worker" TCBs or address spaces. 
Instead of leveraging the existing WLM services -- used by the likes of 
Websphere -- in its design, the System REXX developers decided to use a 
"roll your own" multi-address space server approach. This total lack of 
support for z/OS UNIX services looks to be an unfortunate outcome of 
that questionable decision. :-(


--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/

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


Re: No z/OS UNIX Support in System REXX?

2007-12-06 Thread Patrick O'Keefe
On Tue, 4 Dec 2007 16:12:13 -0800, Edward Jaffe 
<[EMAIL PROTECTED]> wrote:

>IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00110
>ICH408I JOB(AXR04   ) STEP(AXR04   ) CL(PROCESS )
>  OMVS SEGMENT NOT DEFINED
>
>Anyone got this to work?
>...

From
z/OS 1.9 MVS Programming: Authorized Assembler Services Guide
Chapter 31. System REXX

Neither the TSO=YES or TSO=NO environments support UNIX System 
Services host commands.

That doesn't exactly explain why the lack of support should result 
in that RACF error, but it sounds like you are out of luck. 

Time for a requirement?

Pat O'Keefe

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


Re: No z/OS UNIX Support in System REXX?

2007-12-05 Thread Patrick O'Keefe
On Wed, 5 Dec 2007 08:23:58 -0600, Chase, John 
<[EMAIL PROTECTED]> wrote:

>...
>> ICH408I JOB(AXR04   ) STEP(AXR04   ) CL(PROCESS )
>>   OMVS SEGMENT NOT DEFINED
>>
>> Anyone got this to work?
>
>Looks like your job (started task?) needs a userID with an OMVS 
segment.
>...

I could be way off base, but I don't think these responses are 
telling Ed much.  I suspect he is not having trouble interpretting 
that (fairly clear) RACF message.

I don't have access to System Rexx - we're on 1.8, and haven't
downloaded the support - so I have no way of trying it, but I 
suspect the issue is a bit deeper than a RACF definition.
(Either that or he deserves to be on the less common end of an
RTFM than is usually associated with him.)

Pat O'Keefe 


  

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


Re: No z/OS UNIX Support in System REXX?

2007-12-05 Thread Chase, John
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of Edward Jaffe
> 
> IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00110
> ICH408I JOB(AXR04   ) STEP(AXR04   ) CL(PROCESS )
>   OMVS SEGMENT NOT DEFINED
> 
> Anyone got this to work?

Looks like your job (started task?) needs a userID with an OMVS segment.

-jc-

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


Re: No z/OS UNIX Support in System REXX?

2007-12-05 Thread Magen Margalit
Hi,

The user running the job has no OMVS segment you
need the REACF guys to definen such a segment.
(Make sure that the job/stc have an associated user 
 (class started?!?) )

Magen

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


Re: No z/OS UNIX Support in System REXX?

2007-12-04 Thread R.S.

Edward Jaffe wrote:

IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00110
ICH408I JOB(AXR04   ) STEP(AXR04   ) CL(PROCESS )
 OMVS SEGMENT NOT DEFINED


As I know RACF, the message above tell you two things:
1. The job has no RACF user assigned. Otherwise instead of JOB/STEP you 
would see USER/GROUP.
2. The job require OMVS segment. So, the user assigned to the job should 
have OMVS segment as well as his current connect group (usually default 
group). The segemnt can be also assigned via BPX.DEFAULT.USER.



HTH

--
Radoslaw Skorupka
Lodz, Poland


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

Sd Rejonowy dla m. st. Warszawy 
XII Wydzia Gospodarczy Krajowego Rejestru Sdowego, 
nr rejestru przedsibiorców KRS 025237

NIP: 526-021-50-88
Wedug stanu na dzie 01.01.2007 r. kapita zakadowy BRE Banku SA (w caoci 
opacony) wynosi 118.064.140 z. W zwizku z realizacj warunkowego 
podwyszenia kapitau zakadowego, na podstawie uchwa XVI WZ z dnia 21.05.2003 
r., kapita zakadowy BRE Banku SA moe ulec podwyszeniu do kwoty 118.760.528 
z. Akcje w podwyszonym kapitale zakadowym bd w caoci opacone.

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


Re: No z/OS UNIX Support in System REXX?

2007-12-04 Thread Bruce Hewson
Hi Ed,

Your address space AXR04 does not have a RACF identitywhich is why the 
ICH408I is reporting JOB and STEP and not USER and GROUP.

Either use a STARTED class entry to assign a User/Group with OMVS segment,

or, somehow, get the Default OMVS UID and GID set up. But I am not sure 
that the default UID/GID would get used since the address space does not 
have valid ACEE.

On Tue, 4 Dec 2007 16:12:13 -0800, Edward Jaffe 
<[EMAIL PROTECTED]> wrote:

>IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00110
>ICH408I JOB(AXR04   ) STEP(AXR04   ) CL(PROCESS )
>  OMVS SEGMENT NOT DEFINED
>
>Anyone got this to work?
>
>--
>Edward E Jaffe
>Phoenix Software International, Inc


Regards
Bruce Hewson

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


No z/OS UNIX Support in System REXX?

2007-12-04 Thread Edward Jaffe

IEF196I IGD103I SMS ALLOCATED TO DDNAME SYS00110
ICH408I JOB(AXR04   ) STEP(AXR04   ) CL(PROCESS )
 OMVS SEGMENT NOT DEFINED

Anyone got this to work?

--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century Blvd, Suite 800
Los Angeles, CA 90045
310-338-0400 x318
[EMAIL PROTECTED]
http://www.phoenixsoftware.com/

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