| View previous topic :: View next topic |
| Author |
Message |
misi01
Advanced
Joined: 02 Dec 2002
Posts: 618
Topics: 172
Location: Stockholm, Sweden
|
 Posted: Sun Jun 12, 2022 7:16 am Post subject: ACF2, Rexx and Execio |
 |
|
Im' allocating and reading a file in TSO using execio and all is working fine, except for one thing.
Every time I do the actual EXECIO, I get the file into a stem variable, but at the same time I get the following ACF2 message
| Quote: |
ACF99900 ACF2 LOGGING-12,00,S6843F,TCCS12,filename......,N/A
|
The actual error message definition can be found here
https://techdocs.broadcom.com/us/en/ca-mainframe-software/security/ca-acf2-for-z-os-messages/1-0/acf90-acf9f-messages/acf99-security-svc-support/acf99900.html
I've googled the meaning of the message and found this URL
https://techdocs.broadcom.com/us/en/ca-mainframe-software/security/ca-acf2-for-z-os/16-0/administrating/administer-rules/access-rules/access-rule-entries.html
under the Execute(Allow|Log|Prevent) heading.
The way I read it, it's just a warning, but I would like to get rid of the message completely if I could.
Does anyone have a suggestion?
BTW. Just did a simple test. We have 4 levels of PDS's from "simple" test to PROD (the one that is causing me "grief").
The first 3 do not issue the ACF message; it's only doing EXECIO on the PROD PDS that causes the message.
So the solution seems "simple".
Either change the access authority on the prod PDS (hmmm, wonder what the security guy will think of that  )
or some kund soul shows me a way to capture the ACF message in Rexx.. I'll include my Rexx code here as well (FWIW)
| Code: |
x = OUTTRAP("alloc.")
address TSO "allocate dd(copy) da('"file"') shr reuse"
if rc <> 0 then
do
/* Failed to allocate */
say 'Failed to allocate file 'file
return ''
end
address TSO "execio * diskr copy (stem copybook. finis"
address TSO "free dd(copy)"
x = OUTTRAP('OFF')
|
_________________
Michael |
|
| Back to top |
|
 |
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12367
Topics: 75
Location: San Jose
|
|
| Back to top |
|
|
misi01
Advanced
Joined: 02 Dec 2002
Posts: 618
Topics: 172
Location: Stockholm, Sweden
|
| Posted: Tue Jun 14, 2022 8:16 am Post subject: |
|
|
Turned out to be even easier than that!
TSO PROFILE NOWTPMSG got rid of the messages (our default at work seems to be WTPMSG for some weird reason, seeing as how the default is NO write)
_________________
Michael |
|
| Back to top |
|
|
kolusu
Site Admin
Joined: 26 Nov 2002
Posts: 12367
Topics: 75
Location: San Jose
|
| Posted: Tue Jun 14, 2022 12:29 pm Post subject: |
|
|
| misi01 wrote: | Turned out to be even easier than that!
TSO PROFILE NOWTPMSG got rid of the messages (our default at work seems to be WTPMSG for some weird reason, seeing as how the default is NO write) |
misi01,
Well the message is still written , but you forcing NOWTPMSG means that you do not see write-to-programmer messages displayed on your terminal. WTPMSG may provide additional error messages if system ABENDs occur during your TSO/E session.
_________________
Kolusu - DFSORT Development Team (IBM)
DFSORT is on the Web at:
www.ibm.com/storage/dfsort
www.linkedin.com/in/kolusu |
|
| Back to top |
|
|
misi01
Advanced
Joined: 02 Dec 2002
Posts: 618
Topics: 172
Location: Stockholm, Sweden
|
| Posted: Sun Jun 26, 2022 10:43 am Post subject: |
|
|
What i do now is save the profile setting, set it to NO.... and then reset it to the saved value on exit.
The fact that a THEORETICAL abend MIGHT be missed? I can live with that in order to eliminate those tiresome messages.
_________________
Michael |
|
| Back to top |
|
|
|
|
|
FAQ
Search
Quick Manuals
Register
Profile
Log in to check your private messages
Log in
