Re: ATTACHX/STIMERM WAIT=YES

2023-11-13 Thread Tony Harminc
On Mon, 13 Nov 2023 at 19:37, Paul Schuster wrote: > How to handle this situation: task ‘A’ attaches a subtask, task ‘B’. > > The ‘B’ task issues a STIMERM WAIT=YES > > Task ‘A’ terminates, but gets the A03 abend since task ‘B’ still active. > > How can task ‘A’ communicate to the subtask ‘B’

Re: ATTACHX/STIMERM WAIT=YES

2023-11-13 Thread Steve Thompson
Just off the top of my head from having a similar issue a few years ago, you may need to be watching two ECBs (EVENTS). But I'm not sure that the STIMERM won't cause a squawk when you have the task end. And I think you will have to pass the address of the ECB you will POST for termination

Re: ATTACHX/STIMERM WAIT=YES

2023-11-13 Thread Seymour J Metz
DETACH? Or do you need something less disruptive? -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי From: IBM Mainframe Discussion List on behalf of Paul Schuster Sent: Monday, November 13, 2023 7:37 PM To:

ATTACHX/STIMERM WAIT=YES

2023-11-13 Thread Paul Schuster
How to handle this situation: task ‘A’ attaches a subtask, task ‘B’. The ‘B’ task issues a STIMERM WAIT=YES Task ‘A’ terminates, but gets the A03 abend since task ‘B’ still active. How can task ‘A’ communicate to the subtask ‘B’ that it (task ‘B’) needs to terminate? Task ‘B’ is in the

Re: UNIX "BLKSIZE"?

2023-11-13 Thread Paul Gilmartin
On Mon, 13 Nov 2023 19:09:26 -0500, Tony Harminc wrote: >> >> >>On Mon, 13 Nov 2023 01:10:14 -0600, Jon Perryman >> wrote: >> >>z/OS Unix filesystems are linear datasets. > >Some are. > Exceptions might be sockets, descriptors, pipes, and NFS. And not all UNIX files belong to filesystems. >>No.

Re: UNIX "BLKSIZE"?

2023-11-13 Thread Tony Harminc
On Mon, 13 Nov 2023 at 13:54, Jon Perryman wrote: > On Mon, 13 Nov 2023 09:11:19 -0600, Paul Gilmartin > wrote: > > >>On Mon, 13 Nov 2023 01:10:14 -0600, Jon Perryman > wrote: > >>z/OS Unix filesystems are linear datasets. > Some are. >No. BLKSIZE is not ignored. > > Incorrect, BLKSIZE has

Re: UNIX "BLKSIZE"?

2023-11-13 Thread Seymour J Metz
While BLKSIZE has no meaning for linear data sets, it *does* have meaning for the BSAM compatibiliy interface. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי From: IBM Mainframe Discussion List on behalf of Jon Perryman

Re: RACF, the FACILITY class, and z/XDC

2023-11-13 Thread David Cole
Hi Jon, Thanks for your thoughts, but I'm not trying to decide if I should use FACILITY. I'm trying to decide how I should go about discontinuing using FACILITY. Based on suggestions from others on this thread, I've made the decision to switch to using a class named XFACILIT. [Switching

Re: RACF, the FACILITY class, and z/XDC

2023-11-13 Thread Jon Perryman
On Mon, 13 Nov 2023 13:30:56 -0500, David Cole wrote: >so while creating a "$XDC" class perhaps might be "easy", to >paraphrase Peter, why would I make a customer do that when I don't have to... > >So thank you to those who tipped me off about the XFACILIT. It sounds >perfect for my needs.

Re: UNIX "BLKSIZE"?

2023-11-13 Thread Paul Gilmartin
On Mon, 13 Nov 2023 12:54:31 -0600, Jon Perryman wrote: >... >> and probably has some effect on performance for QSAM. > >I'm guessing that performance benefit is insignificant. More important is the >adverse effect of buffering by BSAM / QSAM. It violates the UNIX standard of >concurrent

Re: unable to access IPCS 64 bit storage using Storage map service

2023-11-13 Thread Joseph Reichman
Changing the length to =AD(100) did it thanks Adam > On Nov 13, 2023, at 1:04 PM, Joseph Reichman wrote: > > I’m using test to debug this thanks > >>> On Nov 13, 2023, at 11:28 AM, Adam Johanson >>> <031ca9d720a7-dmarc-requ...@listserv.ua.edu> wrote: >>> >>> Joe wrote: >>> I got a

Re: RACF, the FACILITY class, and z/XDC

2023-11-13 Thread Binyamin Dissen
On Mon, 13 Nov 2023 12:58:16 + Peter Relson wrote: :>Regardless of whether it is hard or easy, why would you :>want to bother creating a new class when there is an :>existing class (XFACILIT) that completely addresses the problem :>(and thus would be easier for a customer)? DEFAULTRC

Re: UNIX "BLKSIZE"?

2023-11-13 Thread Jon Perryman
On Mon, 13 Nov 2023 09:11:19 -0600, Paul Gilmartin wrote: >>On Mon, 13 Nov 2023 01:10:14 -0600, Jon Perryman wrote: >>z/OS Unix filesystems are linear datasets. >No. BLKSIZE is not ignored. Incorrect, BLKSIZE has no meaning for VSAM linear datasets. By definition, "All linear data set

RACF, the FACILITY class, and z/XDC

2023-11-13 Thread David Cole
Gadi, Binyamin, Rob, Ed, Phil, Hayim and Peter! Thank you all for good information and a GREAT discussion! Like some of you, I also am very sensitive to the customer's burden, so while creating a "$XDC" class perhaps might be "easy", to paraphrase Peter, why would I make a customer do that

Re: unable to access IPCS 64 bit storage using Storage map service

2023-11-13 Thread Joseph Reichman
I’m using test to debug this thanks > On Nov 13, 2023, at 11:28 AM, Adam Johanson > <031ca9d720a7-dmarc-requ...@listserv.ua.edu> wrote: > > Joe wrote: >> I got a number of responses but I decided to use the post By Adam Johanson >> using storage map services below is my code > > It

Re: erroneous BLS18100I message

2023-11-13 Thread Adam Johanson
John P. wrote: > VERBX VSMDATA should show allocated 64 storage. You have to use the RSMDATA subcommand to see the above-the-bar allocations. As a starting point, see RSMDATA HIGHVIRTUAL . === Adam Johanson Broadcom Mainframe Software Division

Re: unable to access IPCS 64 bit storage using Storage map service

2023-11-13 Thread Adam Johanson
Joe wrote: > I got a number of responses but I decided to use the post By Adam Johanson > using storage map services below is my code It appears that I am now pot-committed to this thread, so here goes. John P. wrote: > My suggestion would be to start from a function use of ADPLSACC which

Re: UNIX "BLKSIZE"?

2023-11-13 Thread Paul Gilmartin
On Mon, 13 Nov 2023 01:10:14 -0600, Jon Perryman wrote: > >>Suppose I am writing with QSAM/BSAM to a UNIX file allocated >>RECFM=FB,LRECL=80,FILEDATA=BINARY,PATH=... >>Should I specify: >>o BLKSIZE=80 for minimum latency for other jobs doing "tail -f"? > >z/OS Unix filesystems are linear

Re: Is True Skip-Sequential Processing Possible with RECFM=FB,DSORG=PS?

2023-11-13 Thread Seymour J Metz
XDAP is basically EXCP with some housekeeping for DASD. -- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 עַם יִשְׂרָאֵל חַי From: IBM Mainframe Discussion List on behalf of Attila Fogarasi Sent: Sunday, November 12, 2023 5:30 PM To:

Re: RACF, the FACILITY class, and z/XDC

2023-11-13 Thread Hayim Sokolsky
While some have suggested creating your own class, there is an off-the-shelf class suitable for XDC's use: XFACILIT. - Maximum resource length is 246 - Default return code is 8 (everything is denied if the resource is not defined) This is just as suitable as creating your own class name, and

Re: PC Interference from shredder Was: Kinda fun

2023-11-13 Thread Bob Bridges
This is why I have some sympathy for the military guys who have to decide what knowledge to classify. We're told all the horror stories about stupidly-held secrets that don't need to be secrets, and it isn’t that I don't believe them. And the boundaries of one military airfield may not be

Re: RACF, the FACILITY class, and z/XDC

2023-11-13 Thread Peter Relson
Regardless of whether it is hard or easy, why would you want to bother creating a new class when there is an existing class (XFACILIT) that completely addresses the problem (and thus would be easier for a customer)? Peter Relson z/OS Core Technology Design

Re: RACF, the FACILITY class, and z/XDC

2023-11-13 Thread Rob Scott
Although setting up your own SAF class is not difficult, it is another step in the installation/migration process and my instinct (bearing in mind the squeeze on staffing resources) is always to tend to "zero-config" wherever possible. If you stay within your lanes as far as the profile

Re: erroneous BLS18100I message

2023-11-13 Thread Jon Perryman
On Sun, 12 Nov 2023 22:35:12 -0500, Joseph Reichman wrote: >I got the following message tracing VERBX routine under TEST >BLS18100I ASID(X'0040') 01EF_8550 not available > >Yet when I do the following running IPCS from the TSO command prompt > LIST 01EF_8550. ASID(X'0040') LENGTH(X'64')