View previous topic :: View next topic |
Author |
Message |
raj051076 Beginner
Joined: 05 Dec 2002 Posts: 64 Topics: 21
|
Posted: Fri Dec 13, 2002 12:56 am Post subject: |
|
|
code X=MSG("OFF") at the very beginning. _________________ Rajib |
|
Back to top |
|
 |
raj051076 Beginner
Joined: 05 Dec 2002 Posts: 64 Topics: 21
|
Posted: Fri Dec 13, 2002 12:57 am Post subject: |
|
|
one more thing code ADDRESS TSO "FREE F(<DDNAME>)" before opening any file. _________________ Rajib |
|
Back to top |
|
 |
raj051076 Beginner
Joined: 05 Dec 2002 Posts: 64 Topics: 21
|
Posted: Fri Dec 13, 2002 1:04 pm Post subject: |
|
|
if you do not want any message it is safe to code it as the firat line after/**rexx**/
no address tso is not required but since i have to switch between tso and ispexec I made it a habit to code the address every time. _________________ Rajib |
|
Back to top |
|
 |
tidda Beginner

Joined: 02 Dec 2002 Posts: 24 Topics: 6 Location: India
|
Posted: Sat Dec 14, 2002 4:09 pm Post subject: |
|
|
i'm a novice to rexx/ispf. pls let me know if i'm going wrong somewhere. In the problem mentioned by ravi, will it be helpful 'outtrap' the message and continue processing accordingly ?
tidda |
|
Back to top |
|
 |
Mike Beginner

Joined: 03 Dec 2002 Posts: 114 Topics: 0 Location: Sydney, Australia
|
Posted: Wed Dec 18, 2002 8:18 pm Post subject: |
|
|
My understanding is that MSG("Off") only traps TSO/E messages e.g. the IKJ messges. IRX messages are Rexx messages and as such are not catered for by the MSG function. As EXECIO is a Rexx function, as oppsoed to ALLOC, which is a TSO/E function, it issues Rexx messages.
Why not use something like :-
Code: |
rcode = LISTDSI(OUTDD1 FILE)
If rcode <= 4 Then Do
"EXECIO 1 DISKW OUTDD1"
"EXECIO 0 DISKW OUTDD1"
End
Else Say "My custom message"
|
Thus using LISTDSI to predict if an error would occur. Obviously this wouldn't detect all possible errors (e.g. an SB37). _________________ Regards,
Mike. |
|
Back to top |
|
 |
Mike Beginner

Joined: 03 Dec 2002 Posts: 114 Topics: 0 Location: Sydney, Australia
|
Posted: Wed Jan 08, 2003 4:22 pm Post subject: |
|
|
RaviShanker,
I think that the CONSPROF is for use when you have been given the ability to connect as a console (e.g. like an operator), hence why you get the authority problem.
With regard to not getting the message, you could get around this by submitting a batch job to do the recall. The problem you then have is monitoring for the job's completion. This could be done via the STATUS command or possibly by letting the job create a dataset, which you then check for.
Obviously this checking would have to be done within a loop and you would probably want to implement some method of reducing the CPU usage. See if the OPSWAIT command is available (people have said that this is an externally supplied command, however when I look it up in Quickref it's in TSO/SYSHELP). If not the topic of non-cpu intensive looping is raised quite frequently and alternative solutions are given. I have my own solution which is written as a Rexx function in assembler (although I now utilise OPSWAIT). If you want this then just let me know and I'll send the source code.
I've tried playing with my TSO PROFILE, using NOINTERCOM and NOWTPMSG, but these do not suppress the messages.
Regards,
Mike. _________________ Regards,
Mike. |
|
Back to top |
|
 |
|
|