On 5/18/2020 10:56 AM, Jousma, David wrote:
My subsequent response was indeed that. My point though is that "su" followed
by some other commands do not appear to be executing as UID(0) authority.
Yes, that's normal and expected behavior. You can see what's happening
if you logon and issue
t: Re: USS: su: User ID "SH" does not exist
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
On 5/18/2020 9:37 AM, Jousma, David wrote:
> //OMVS EXEC PGM=BPXBATCH,REGION=128M
> //SYSPRINT DD SYSOUT=
On 5/18/2020 9:37 AM, Jousma, David wrote:
//OMVS EXEC PGM=BPXBATCH,REGION=128M
//SYSPRINT DD SYSOUT=*
//SYSTSPRT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//STDPARM DD *
SH su;
ps -ef
/*
For that I would try: echo ps -ef | su
--
Phoenix Software International
Edward E. Jaffe
831
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
On Mon, 18 May 2020 16:37:09 +, Jousma, David wrote:
>...
>Yet,
On Mon, 18 May 2020 16:37:09 +, Jousma, David wrote:
>...
>Yet, I only see PID's associated my own UID instead of UID(0)
>...
It's a security feature, enforced mostly by IBM. SDSF may allow
finer-grained control. From the Command Ref. for ps:
... However, these
2020 12:20 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
**CAUTION EXTERNAL EMAIL**
**DO NOT open attachments or click on links from unknown senders or unexpected
emails**
On 5/14/2020 5:23 PM, Jon Bathmaker wrote:
> //STDPARM DD *
> SH su
> S
U
Subject: Re: USS: su: User ID "SH" does not exist
On Fri, 15 May 2020 at 12:38, Seymour J Metz wrote:
>
> I thought that you could turn off TSO recognition of semicolon with
PROFILE or TERMINAL but, no, you can't. I'm not sure what happens if CLIST
or REXX code passes a semicol
On Fri, 15 May 2020 at 12:38, Seymour J Metz wrote:
>
> I thought that you could turn off TSO recognition of semicolon with
PROFILE or TERMINAL but, no, you can't. I'm not sure what happens if CLIST
or REXX code passes a semicolon. OTOH, TSO will accept a semicolon in a
quoted string.
Semicolon
ERV.UA.EDU] on behalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Friday, May 15, 2020 12:47 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
On Fri, 15 May 2020 16:38:04 +, Seymour J Metz wrote:
>I thought that
On Fri, 15 May 2020 12:04:42 -0500, Kirk Wolf wrote:
>On Fri, May 15, 2020 at 11:44 AM Seymour J Metz wrote:
>
>Which documentations describes the SH concatenation for other than
>> instream? Also, where in the documentation does it say that it inserts
>> whitespace after each record?
>>
>You are
of Kirk Wolf [k...@wolf-associates.com]
> Sent: Friday, May 15, 2020 12:26 PM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: USS: su: User ID "SH" does not exist
>
> Jack,
> I would disagree with your explanation of why BPXBATCH works so poorly ;-)
>
> In the OP's ex
On Fri, 15 May 2020 16:38:04 +, Seymour J Metz wrote:
>I thought that you could turn off TSO recognition of semicolon with PROFILE or
>TERMINAL but, no, you can't. I'm not sure what happens if CLIST or REXX code
>passes a semicolon. OTOH, TSO will accept a semicolon in a quoted string.
>
I
Gil,
Some people hate EBCDIC, others BPXBATCH :-)
On Fri, May 15, 2020 at 11:35 AM Paul Gilmartin <
000433f07816-dmarc-requ...@listserv.ua.edu> wrote:
> On Fri, 15 May 2020 11:26:29 -0500, Kirk Wolf wrote:
> >
> >STDPARM washes away the record boundaries (see the doc). The semicolons
> >
>
://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Kirk Wolf [k...@wolf-associates.com]
Sent: Friday, May 15, 2020 12:26 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exis
:22 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
On Fri, 15 May 2020 14:02:25 +, Seymour J Metz wrote:
>Semicolon is a separator for TSO SH as well, but you have to keep TSO from
>recognizing it.
>
Can it be quoted or escaped? Wha
On Fri, 15 May 2020 11:26:29 -0500, Kirk Wolf wrote:
>
>STDPARM washes away the record boundaries (see the doc). The semicolons
>
What if you start each line with x'15'?
ISPF Edit change all ';' x'15 1 1'?
>are required at the end of DD:STDPARM records so that this single argument
>to "/bin/sh
Jack,
I would disagree with your explanation of why BPXBATCH works so poorly ;-)
In the OP's example, DD STDPARM is used to construct a single PARM string
that ends up getting passed to BPXBATCH.
What BPXBATCH does is look at the leading "SH" in it's PARM and then pass
the rest of the string as
On Fri, 15 May 2020 14:02:25 +, Seymour J Metz wrote:
>Semicolon is a separator for TSO SH as well, but you have to keep TSO from
>recognizing it.
>
Can it be quoted or escaped? What about on the ISPF command line?
Where is the "TSO SH" command described? TSO Command Ref? UNIX Command
On Fri, 15 May 2020 15:43:34 +, Seymour J Metz wrote:
>I hate that URL mangling!
>https://www.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.bpxa500/bpxbatr.htm
>
And that one didn't get mangled. It's the Command Ref.
>IBM Knowledge Center
>
> Home -> z/OS 2.1.0 -> z/OS
On Fri, 15 May 2020 09:12:36 -0600, Jack J. Woehr wrote:
>
>There are shell features like "here documents" (google it) which you've
>probably never used that would get broken if input to the USS shell got
>arbitrarily broken into lines to suit the flavor of MVS/TSO/JES
>
Au contraire. Here
ehalf of
Paul Gilmartin [000433f07816-dmarc-requ...@listserv.ua.edu]
Sent: Friday, May 15, 2020 11:08 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
On Fri, 15 May 2020 13:35:59 +, Seymour J Metz wrote:
>"For in-stream data
On Fri, 15 May 2020 09:30:46 -0500, Joel C. Ewing wrote:
>I think that maybe they are trying to imply ..l.
>
Stop! That's not how to document.
On Fri, 15 May 2020 14:51:10 +, Seymour J Metz wrote:
>
>I understand why they parse pgm and sh differently. What I don't understand is
>why
On 5/15/20 8:51 AM, Seymour J Metz wrote:
I understand why they parse pgm and sh differently. What I don't understand is
why instream data should be treated differently from other datasets.
Because it's easier to present to the Unix System Services environment
that way?
Unix is stream
On Fri, 15 May 2020 13:35:59 +, Seymour J Metz wrote:
>"For in-stream data sets: with the SH option, trailing blanks are not
>truncated. Records in in-stream data sets are concatenated with blanks as
>separator characters, and the string remaining after the SH token is passed as
>a single
of
Joel C. Ewing
Sent: Friday, May 15, 2020 10:30 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
I think that maybe they are trying to imply that if "PGM" is used, the
whole rest of the multi-line string is parsed as MVS-style program
par
rom: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
> Jon Bathmaker [jon.bathma...@sys1consulting.com]
> Sent: Friday, May 15, 2020 8:10 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Re: USS: su: User ID "SH" does not exist
>
> Hi Ed,
>
> Tha
Jon,
You have to email the listserv for everyone to see your note. See
instructions at the bottom of this post.
All,
I think I've posted this before, but this is how I avoid semi-colons and
plus signs. I just have a job where I can type normal commands and see the
output as I'd like.
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
I'm talking about the TSO SH command not a shell script!
On 2020-05-15 9:13 PM, Joel C. Ewing wrote:
> Nope. In Unix, semicolons are command separators, not a continuation
> indicator. The actual comm
I'm talking about the TSO SH command not a shell script!
On 2020-05-15 9:13 PM, Joel C. Ewing wrote:
Nope. In Unix, semicolons are command separators, not a continuation
indicator. The actual command continuation character is "\", but that
is only needed just prior to an EOL character.
It
@LISTSERV.UA.EDU] on behalf of
David Spiegel [dspiegel...@hotmail.com]
Sent: Friday, May 15, 2020 9:36 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
Hi R'Shmuel,
BPXBATCH allows only one Command Buffer. If the user wants to issue more
than one command,
@gmail.com]
Sent: Friday, May 15, 2020 8:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
Nope. Semicolons are a continuation!
On 2020-05-15 8:13 PM, David Spiegel wrote:
Hi Jon,
Every line except for the last line needs a semicolon.
Regards,
David
du/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of Jon
Bathmaker [jon.bathma...@sys1consulting.com]
Sent: Friday, May 15, 2020 8:10 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
Hi Ed,
Thanks for this! How *did
...@gmail.com]
Sent: Friday, May 15, 2020 9:25 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
Yes, in a shell, but no using BPXBATCH.
On 2020-05-15 9:17 PM, Seymour J Metz wrote:
> ITYM \ at the end is a continuation.
>
>
> --
> Shmuel
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List [IBM-MAIN@LISTSERV.UA.EDU] on behalf of
Joel C. Ewing [jcew...@acm.org]
Sent: Friday, May 15, 2020 9:13 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID
Hi David,
Yes, I am aware of that. That is *why* they are necessary.
What is your point?
Regards,
David
On 2020-05-15 08:47, David Crayford wrote:
Nope. Semicolons are a continuation!
On 2020-05-15 8:13 PM, David Spiegel wrote:
Hi Jon,
Every line except for the last line needs a semicolon.
of
David Crayford [dcrayf...@gmail.com]
Sent: Friday, May 15, 2020 8:47 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
Nope. Semicolons are a continuation!
On 2020-05-15 8:13 PM, David Spiegel wrote:
Hi Jon,
Every line except for the last
-MAIN@LISTSERV.UA.EDU
Subject: Re: USS: su: User ID "SH" does not exist
Nope. Semicolons are a continuation!
On 2020-05-15 8:13 PM, David Spiegel wrote:
> Hi Jon,
> Every line except for the last line needs a semicolon.
>
> Regards,
> David
>
> On 2020-05-15 08:10
Nope. In Unix, semicolons are command separators, not a continuation
indicator. The actual command continuation character is "\", but that
is only needed just prior to an EOL character.
It would appear that in this environment no end-of-line characters are
seen, so unix just sees "SH su SH
Use BPXBATSL, Check the fine manuals for details.
-Original Message-
From: IBM Mainframe Discussion List On Behalf Of Jon
Bathmaker
Sent: Thursday, May 14, 2020 7:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: USS: su: User ID "SH" does not exist
[CAUTION: This Email is fr
Nope. Semicolons are a continuation!
On 2020-05-15 8:13 PM, David Spiegel wrote:
Hi Jon,
Every line except for the last line needs a semicolon.
Regards,
David
On 2020-05-15 08:10, Jon Bathmaker wrote:
Hi Ed,
Thanks for this! How *did* you find out about the semicolons, I
didn't see them
Hi Jon,
Every line except for the last line needs a semicolon.
Regards,
David
On 2020-05-15 08:10, Jon Bathmaker wrote:
Hi Ed,
Thanks for this! How *did* you find out about the semicolons, I
didn't see them anywhere in the doc.
Best regards,
*Jon Bathmaker,*
SYS1 Consulting Inc.
Hi Ed,
Thanks for this! How *did* you find out about the semicolons, I didn't
see them anywhere in the doc.
Best regards,
*Jon Bathmaker,*
SYS1 Consulting Inc.
519-577-9661
On 5/15/2020 12:19 AM, Ed Jaffe wrote:
On 5/14/2020 5:23 PM, Jon Bathmaker wrote:
//STDPARM DD *
SH su
SH echo
On 5/14/2020 5:23 PM, Jon Bathmaker wrote:
//STDPARM DD *
SH su
SH echo $PATH
SH unmount -fv ZOS240.SYS1.OMVS.SYSRES.OS240971.FNT.ZFS
The above looks wrong to me. I always do it this way:
//STDPARM DD *
SH su;
echo $PATH;
unmount -fv ZOS240.SYS1.OMVS.SYSRES.OS240971.FNT.ZFS
--
On Thu, 14 May 2020 22:21:27 -0400, Tom Conley wrote:
>
>Try setting up sudo to do the command all at once. "sudo unmount.".
>Using su requires a password that you would not want in the clear.
>
That setup might be in /etc/sudoers or in a RACF BPX.SUPERUSER
privilege class.
On 5/14/2020 8:23 PM, Jon Bathmaker wrote:
Hi,
Because of auditor demands we are no longer able to run TSO USS commands
that require UID=0, so I attempting figure out how to run USS commands
in under BPXBATCH. The following is a job to debug the unmount command
in batch but I have been
On Thu, 14 May 2020 20:23:20 -0400, Jon Bathmaker wrote:
>
>
>//STDERR�� DD SYSOUT=*
>
>//STDOUT� �DD SYSOUT=*
>
>//STDPARM� DD *
>
>SH su
>
>SH echo $PATH
>
>SH unmount -fv ZOS240.SYS1.OMVS.SYSRES.OS240971.FNT.ZFS
>
>Here is the contents of STDERR when the job runs.
>
>FSUM5023 su: User ID "SH"
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of Jon
Bathmaker
Sent: Thursday, May 14, 2020 8:23 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: USS: su: User ID "SH" does not exist
Hi,
Becaus
Hi,
Because of auditor demands we are no longer able to run TSO USS commands
that require UID=0, so I attempting figure out how to run USS commands
in under BPXBATCH. The following is a job to debug the unmount command
in batch but I have been unsuccessful so far. I am hoping that I am
48 matches
Mail list logo
