Hi List
Wow - thanks for input List
Lots of ideas , suggestions and questions.
When you use PARM and not SYSTSIN it doesn’t seem to ECHO input/command. I
tried it before posting so as not to incur wrath of LIST
Walt - correct.. the userid of the mother task is not authorised to ADDUSER.
The ATTACH is done in supervisor state. Don’t try this at home type stuff
Tony - attach worked fine as you stated. See code snippet below.
LIST - I assume if I "front-end" this process it would have to keep the
authorised chain alive? Taking Walts suggestion (but via asm pgm and nor rexx)
and extending it to creating a IKJEFT1X ac(1)?
At risk of being off topic - It raises the question of opening up functionality
via transactional processing(CICS/IMS) to allow RACF users to be added.
Business wants it but by the time you have solved all the auth and audit stuff
you have a monster. (getting from problem state running in an IMS dep region or
CICS AOR to supervisor attaching an auth subtask etc etc and getting v messy)
ATTACH PARAM=(TASKPRM),ECB=TASKECB,
MF=(E,TASKPMA),SF=(E,TASKATT)
ST R1,TASKTCB
LR R3,R15 SAVE I
BAL R8,AUTHRES RESET
LTR R3,R3 IKJEFT
BNZ ATTFAIL NO - D
WAIT ECB=TASKECB
DETACH TASKTCB
L R3,TASKECB ISOLAT
N R3,=X'3FFFFFFF'
LTR R3,R3 TASK R
BNZ CMDFAIL NO - D
Thanks again List
Walt, John, Tony, ITschak, Elardus, et al
-----Original Message-----
From: Tony Harminc [mailto:[email protected]]
Sent: 26 October 2017 08:28 PM
Subject: Re: Batch TSO command (ADDUSER) tracing and diagnostics
On 26 October 2017 at 03:30, Baguley, Nicholas: Absa <
[email protected]> wrote:
> Hi List
>
> We need to echo or trace the TSO commands processed in a batch TSO
> process...
> We are issuing an ADDUSER command under TSO and it returns a RC=8.
> In itself not a "biggie". We run TSO via an ATTACH of IKJEFTnn(1B in
> this
> case) so it is a subtask of an IMS address space.
>
As Walt points out, I don't believe this is a supported thing to do. Unless you
are ATTACHing a new job step task, which raises plenty of other issues.
The ADDUSER command is passed to IKJEFT as a PARM on the attach svc/macro
> as opposed to SYSTSIN.
>
> We don't see the command "echoed" to SYSTSPRT as you "normally" do
> when using SYSTSIN.
> Is anyone aware of a mechanism of switching on tracing or diagnosing
> PARM= input to IKJ?
>
Not directly. But why not invoke a little REXX program from the PARM=, and have
that program report back on the results, return codes, and so on of the actual
command(s) you issue? You'd need access to this REXX program, but thst'a easily
done with a SYSEXEC or SYSPROC DD.
>
> NB - this works fine in 99% of cases.
Which suggests that your TMP is working via your ATTACH. Curious...
Tony H.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO IBM-MAIN
Important Notice:
Absa is an Authorised Financial Services Provider and Registered Credit
Provider,
registration number: NCRCP7. This e-mail and any files transmitted with it may
contain information that is confidential, privileged or otherwise protected
from
disclosure. If you are not an intended recipient of this e-mail, do not
duplicate
or redistribute it by any means. Please delete it and any attachments and
notify
the sender that you have received it in error. Unless specifically indicated,
this
e-mail is not an offer to buy or sell or a solicitation to buy or sell any
securities,
investment products or other financial product or service, an official
confirmation of
any transaction, or an official statement of Absa. Any views or opinions
presented
are solely those of the author and do not necessarily represent those of Absa.
This e-mail is subject to terms available at the following link:
http://www.absa.co.za/disclaimer.
The Disclaimer forms part of the content of this email. If you are unable to
access
the Disclaimer, send a blank e-mail to [email protected] and we will send
you a
copy of the Disclaimer. By messaging with Absa you consent to the foregoing.
By emailing Absa you consent to the terms herein. This email may relate to or
be sent
from other members of the Absa Group.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
