Re: Issues while compiling SVC exit on Z1.10

[John McKown]

On Tue, Oct 13, 2015 at 12:17 AM, David Crayford 
wrote:

> On 13/10/2015 11:08 AM, John McKown wrote:
>
>> ​I am assuming that, like where I work, the people in charge of the money
>> don't want to spend it. I recall you mentioning my JES2DISK. It is not on
>> the CBTtape, but can be downloaded here:
>>
>> https://gist.github.com/JohnArchieMckown/b27747d0c4750a258997
>>
>> That is a "gist" on the GitHub site. There is a button the right hand side
>> labeled "Download ZIP" for "normal" people (i.e. people who don't use the
>> git SCM system). The OP can click on that, unzip the file on his PC (I
>> assume Windows because that what most people run, despite my opinion of it
>> and MS).
>>
>
> What I normally do with gists is switch to raw view, copy the URL and then
> use curl to download the file from a z/OS Unix shell. I can redirect the
> output to either a Unix file or MVS data set.
> I find that much more convenient than the download to workstation, unzip,
> FTP to z/OS pipeline.
>

​That is a nice way to do it. In this specific case, I am not too sure that
the OP has enough z/OS UNIX experience to do that. I get the impression
that he perhaps he is rather new in this arena. But perhaps I'm selling him
short. If so, I offer my apologies.​

-- 

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Invoke AMODE31-only Code from AMODE64

[Peter Relson]

>Yes, as long as the code is RMODE31 you can use BASSM to
>switch modes; I don't recommend Set Addressing Mode.

I quite strongly disagree.

You often are required to use the linkage instruction that the target 
routine expects you to use.
If you are to use a macro, then the macro will use that linkage 
instruction.
If the documentation is "CALL" then you should use that (and it will 
generate BASR or BALR, but not BASSM).
Of course you can BASSM to "yourself" so that you can get to the real 
target via subsequent BASR/BALR.

Simply put, a service routine needs to know whether it is BASR-entered or 
BASSM-entered in order to know how to determine the caller's AMODE.
Many routines will begin with "BSM 14,0" to "capture the current AMODE" 
perhaps in order that they can issue BAKR and have the corresponding PR 
work. If the routine expects to be entered by BASSM it will not do this. 
If it expects to be entered by BASR it can be necessary. If the wrong 
choice is taken, control will not return properly. And the responsibility 
is on the caller to do what the target documents (or use what the target 
provides as the calling mechanism).

>It depends on the SVC. The Diagnosis book describes the 
>register requirements.

It is never a system requirement to provide R13 for an SVC.
I think, in general, that only the LINK SVC (and the LINKX extended SVC), 
and SYNCH might return control with regs 2-13 not preserved. For those the 
R13 requirement is an attribute of the target routine. If the target 
routine chooses not to have such a requirement -- perhaps it uses BAKR/PR 
-- then it imposes no such requirement on the invoker.

Peter
rel...@us.ibm.com 
 1-845-435-83908+295-8390

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Syncsort changes hands

[Charles Mills]

www.businesswire.com/news/home/20151012005469/en/Clearlake-Capital-Acquire-B
ig-Data-Software-Provider#.Vh0R1flVhBc 

Charles 

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Invoke AMODE31-only Code from AMODE64

[Don Poitras]

In article 
 you 
wrote:
> >Yes, as long as the code is RMODE31 you can use BASSM to
> >switch modes; I don't recommend Set Addressing Mode.

> I quite strongly disagree.

> You often are required to use the linkage instruction that the target 
> routine expects you to use.
> If you are to use a macro, then the macro will use that linkage 
> instruction.
> If the documentation is "CALL" then you should use that (and it will 
> generate BASR or BALR, but not BASSM).
> Of course you can BASSM to "yourself" so that you can get to the real 
> target via subsequent BASR/BALR.

> Simply put, a service routine needs to know whether it is BASR-entered or 
> BASSM-entered in order to know how to determine the caller's AMODE.
> Many routines will begin with "BSM 14,0" to "capture the current AMODE" 
> perhaps in order that they can issue BAKR and have the corresponding PR 
> work. If the routine expects to be entered by BASSM it will not do this. 
> If it expects to be entered by BASR it can be necessary. If the wrong 
> choice is taken, control will not return properly. And the responsibility 
> is on the caller to do what the target documents (or use what the target 
> provides as the calling mechanism).

> >It depends on the SVC. The Diagnosis book describes the 
> >register requirements.

> It is never a system requirement to provide R13 for an SVC.
> I think, in general, that only the LINK SVC (and the LINKX extended SVC), 
> and SYNCH might return control with regs 2-13 not preserved. For those the 
> R13 requirement is an attribute of the target routine. If the target 
> routine chooses not to have such a requirement -- perhaps it uses BAKR/PR 
> -- then it imposes no such requirement on the invoker.

Then the doc for SVCs 68, 138 should be fixed.

> Peter
> rel...@us.ibm.com 
>  1-845-435-83908+295-8390

-- 
Don Poitras - SAS Development  -  SAS Institute Inc. - SAS Campus Drive
sas...@sas.com   (919) 531-5637Cary, NC 27513

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Issues while compiling SVC exit on Z1.10

[Rakesh Kotha]

Thanks John for your code. Probably you may want to upload to CBT if you want 
to make it available to larger audience.

And yes I am just with 5 years of exp on MF but good at REXX. I am able to 
understand your code and configure to suit to our naming standards.

This might not solve entire requirement(may need to tell management to look for 
vendor product) but good one intern.

Thanks to everyone replied.

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

An article (not IBM oriented) for the COBOL lovers out there.

[John McKown]

http://opensource.com/life/15/10/open-source-cobol-development

GnuCOBOL - have it on Linux/Intel. works well.

OpenCobolIDE - just downloaded it (Fedora Linux 22 x86_64)

COBOL Bridge for Node.js - for those who yearn to embed COBOL in there web
pages. - again, just downloaded it. For the truly strange progammer? [grin].

-- 

Schrodinger's backup: The condition of any backup is unknown until a
restore is attempted.

Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.

He's about as useful as a wax frying pan.

10 to the 12th power microphones = 1 Megaphone

Maranatha! <><
John McKown

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Invoke AMODE31-only Code from AMODE64

[Paul Gilmartin]

On Tue, 13 Oct 2015 07:58:15 -0400, Peter Relson wrote:
>
>It is never a system requirement to provide R13 for an SVC.
>
Which is probably a Good Thing lest the SVC handler do STM 14,12,12(13)
with elevated privilege.

>I think, in general, that only the LINK SVC (and the LINKX extended SVC),
>and SYNCH might return control with regs 2-13 not preserved. For those the
>R13 requirement is an attribute of the target routine. 
> 
And the target routine is not entered with higher privilege than the caller.

-- gil

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Using MGCRE with JES2 Commands

[Neil Duffee]

Looking in from *way* outside, I wonder that the problem might *not* be 
security.  The message states simply there was a non-zero RC.  (Ok, security 
could cause that too.)

Does the MGCRE interface indicate which sub-system the command is to be 
directed to?  Perhaps it should only be D SPOOL without the sub-system 
identifier ($).  Alternately, could there be something in between ie. for SDSF, 
you use /$D SPOOL.

Again, n00b response to be ignored as such.

>  signature = 8 lines follows  <
Neil Duffee, Joe Sysprog, uOttawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585  fax:1 613 562 5161
mailto:NDuffee of uOttawa.ca http:/ /aix1.uOttawa.ca/ ~nduffee
"How *do* you plan for something like that?"  Guardian Bob, Reboot
"For every action, there is an equal and opposite criticism."
"Systems Programming: Guilty, until proven innocent"  John Norgauer 2004
"Schrodinger's backup: The condition of any backup is unknown until a restore 
is attempted."  John McKown 2015


-Original Message-
From: Terry Sambrooks [mailto:terr...sam...@btc...com] 
Sent: October 12, 2015 11:17
Subject: Re: Using MGCRE with JES2 Commands

In respect of "Please post the full IEE707I message and the command attempted." 
The reality is that ANY z/OS command is accepted but ANY JES2 command is 
rejected so if I use $DSPOOL as an example the message received
is:

IEE707I $DSPOOL NOT EXECUTED

If the program were not linked AC(1) it would SD22 which it does not. I am the 
security guy and as such own JES%.** which ought to give me access to commands 
which do not have an explicit profile, or so I thought. [snip]

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: What is a request block prefix?

[michelbutz]

It's in the data areas for RB IHARB the RB like TCB 
Seems to have a prefix 

Sent from my iPhone

> On Oct 13, 2015, at 5:01 PM, Lindy Mayfield  wrote:
> 
> In the system completion codes documentation it says that for an abend FDB 
> that register 2 points to the request block prefix.  What is a 'request block 
> prefix' in this context?
> 
> Verbatim it reads:
> "When nn is not equal to 13, 14, 17, or 37, the system records in register 2 
> the address of the request block prefix for the program that issued the 
> incorrect SVC."
> 
> Thanks in advance for any advice.
> Regards,
> Lindy
> 
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

What is a request block prefix?

[Lindy Mayfield]

In the system completion codes documentation it says that for an abend FDB that 
register 2 points to the request block prefix.  What is a 'request block 
prefix' in this context?

Verbatim it reads:
"When nn is not equal to 13, 14, 17, or 37, the system records in register 2 
the address of the request block prefix for the program that issued the 
incorrect SVC."

Thanks in advance for any advice.
Regards,
Lindy

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Invoke AMODE31-only Code from AMODE64

[Shmuel Metz (Seymour J.)]

In , on 10/13/2015
   at 05:26 AM, Binyamin Dissen  said:

>Of course it does. You can cobble an in between to play the game, 

The thunk is not the service.

>Feel free to show those values where it does not.

When you don't know what mode you'll be called in.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: Invoke AMODE31-only Code from AMODE64

[Shmuel Metz (Seymour J.)]

In
,
on 10/13/2015
   at 07:58 AM, Peter Relson  said:

>I quite strongly disagree.

Why?

>Of course you can BASSM to "yourself" 

Exactly.
 
-- 
 Shmuel (Seymour J.) Metz, SysProg and JOAT
 ISO position; see  
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: (External):Re: What is a request block prefix?

[J O Skip Robinson]

Abend FDB indicates an invalid SVC call. The SVC number is x'DB', or 219, which 
is in the range of installation defined SVCs. In other words, it's not an 
official IBM SVC. Either the SVC environment was set up improperly, or it was 
not an actual SVC call but execution of code that looks like an SVC but isn't. 
You need to find the location where the SVC was issued. Easiest way I know of 
is system trace table. 

.
.
.
J.O.Skip Robinson
Southern California Edison Company
Electric Dragon Team Paddler 
SHARE MVS Program Co-Manager
626-302-7535 Office
323-715-0595 Mobile
jo.skip.robin...@sce.com

-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf 
Of michelbutz
Sent: Tuesday, October 13, 2015 2:03 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: (External):Re: What is a request block prefix?

It's in the data areas for RB IHARB the RB like TCB Seems to have a prefix

Sent from my iPhone

> On Oct 13, 2015, at 5:01 PM, Lindy Mayfield  wrote:
>
> In the system completion codes documentation it says that for an abend FDB 
> that register 2 points to the request block prefix.  What is a 'request block 
> prefix' in this context?
>
> Verbatim it reads:
> "When nn is not equal to 13, 14, 17, or 37, the system records in register 2 
> the address of the request block prefix for the program that issued the 
> incorrect SVC."
>
> Thanks in advance for any advice.
> Regards,
> Lindy

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: An article (not IBM oriented) for the COBOL lovers out there.

[Scott Ford]

Whoaaa Yoda I feel like a mere mortal...love it

On Tuesday, October 13, 2015, John McKown 
wrote:

> http://opensource.com/life/15/10/open-source-cobol-development
>
> GnuCOBOL - have it on Linux/Intel. works well.
>
> OpenCobolIDE - just downloaded it (Fedora Linux 22 x86_64)
>
> COBOL Bridge for Node.js - for those who yearn to embed COBOL in there web
> pages. - again, just downloaded it. For the truly strange progammer?
> [grin].
>
> --
>
> Schrodinger's backup: The condition of any backup is unknown until a
> restore is attempted.
>
> Yoda of Borg, we are. Futile, resistance is, yes. Assimilated, you will be.
>
> He's about as useful as a wax frying pan.
>
> 10 to the 12th power microphones = 1 Megaphone
>
> Maranatha! <><
> John McKown
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu  with the message:
> INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN

Re: RC=8 during SMP/E LINK

[Scott Ford]

Alan,

I agree mixing a library for sure .

Scott

On Monday, October 12, 2015, Staller, Allan  wrote:

> Seems like you are missing a library in your call list (most likely
> SYS1`.LINKLIB).
> Add the appropriate dataset to the SMP/E  DDDEF use for the calllib.
>
> On my z/OS 2.1 system. IRRENV00 is a stand-alone LMOD in SYS1.LINKLIB and
> show a CALLLIB of CEE.SCEELKED
>
> Please post the binder parms used and the SMP/E  DDFEF concatenation of
> the BINDER syslib.
>
> 
> During a SMP/E LINK CALLLIBS we get a RC=8 for module B8RENVXX which is
> part of the RACF Offline feature of the zSecure Suite (FMID HB8R21G) with
> following messages:
>
> IEW2322I 1220  22ALIAS   B8RSR000(SR)
> IEW2322I 1220  23INCLUDE SMPLTS(B8RENVXX)
>  SEQ #
> IEW2322I 1220  24NAME B8RENVXX(R)   MAX ACCEPTABLE
> RC=04
> IEW2648E 5111 ENTRY IRRENV00 IS NOT A CSECT OR AN EXTERNAL NAME IN THE
> MODULE.
> IEW2612E 4327 EXTERNAL SYMBOL AD IS NOT DEFINED FOR ALIAS B8RAD000.
> IEW2612E 4327 EXTERNAL SYMBOL AG IS NOT DEFINED FOR ALIAS B8RAG000.
> IEW2612E 4327 EXTERNAL SYMBOL AU IS NOT DEFINED FOR ALIAS B8RAU000.
> ...
>
> BTW: The LINK is part of a z/OS V1.13  to V2.1 migration, and the RACF
> Offline FMID is installed in a different CSI than z/OS V2.1 Security Server
> (RACF).
> 
>
> --
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to lists...@listserv.ua.edu  with the message:
> INFO IBM-MAIN
>

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN