IBM Mainframe Forum

by **doctorfabiani** » Fri Apr 28, 2017 1:46 pm

hi all ,
I am new here , thanks for each support.
I am facing this issue : I would like to clean the spool of messages while I login TSO after prompting ID and psw.
I am still receiving messages of a failed TSO XMIT and I am not able to delete them (I attached the file with the spool).
Is here some one could help me ?
Thanks in advance.

by **NicC** » Fri Apr 28, 2017 2:19 pm

Pleaase do not use attachments - a simple cut and paste (using the code tags) will do nicely as you can see in other posts.

Has that failed XMIT neen fixed?

by **doctorfabiani** » Fri Apr 28, 2017 2:20 pm

NicC wrote:Pleaase do not use attachments - a simple cut and paste (using the code tags) will do nicely as you can see in other posts.

Has that failed XMIT neen fixed?

No, because I did not need it any more.
Thanks for reply

by **doctorfabiani** » Fri Apr 28, 2017 4:16 pm

hi , this is cut & paste of issue.
Thanks for support

Select all

  SPF DATASETS ALLOCATED                                                        
 INMR931I Acknowledgment from ATXFOGG on MVSADM1                                
 INMR932I   Dataset 'QCHTS.SVT8BH.QCHBTIF' sent 12 DECEMBER 2016 22:52:48.  STOR
ED                                                                              
 IEC030I B37-04,IFG0554A,ATXFOGG,LOGONAT,SYS00049,B18D,TSO003,                  
 ATXFOGG.LOG.MISC                                                               
 INMR030I RECEIVE command terminated.  ABEND B37                                
 INMR031I Register 15 value at ABEND was X'00000004'                            
 IKJ56641I RECEIVE  ENDED DUE TO ERROR+                                         
 READY
IEA995I SYMPTOM DUMP OUTPUT                                             
SYSTEM COMPLETION CODE=B37  REASON CODE=00000004                        
 TIME=12.43.27  SEQ=64137  CPU=0000  ASID=021E                          
 PSW AT TIME OF ERROR  075C1000   80E06996  ILC 2  INTC 0D              
   NO ACTIVE MODULE FOUND                                               
   NAME=UNKNOWN                                                         
   DATA AT PSW  00E06990 - 41003038  0A0DB20A  00509808                 
   AR/GR 0: 008BEE68/00000000_00E06BA4   1: 00000000/00000000_A4B37000  
         2: 00000000/C1E3E7C6_00029E70   3: 00000000/00000000_00E06B6C  
         4: 00000000/C1E3E7C6_008B44A8   5: 00000000/00000000_00E1E000  
         6: 00000000/00000000_008B474C   7: 00000000/00000000_008B47A4  
         8: 00000000/00000000_008B476C   9: 00000000/00000000_008B4030  
***                                                                     
         A: 00000000/00000000_00FC71C0   B: 00000000/00000000_00E06622
         C: 00000000/00000000_008D2128   D: 00000000/00000000_7F56ECE8
         E: 00000000/00000000_00E06622   F: 00000000/00000000_00000004
 END OF SYMPTOM DUMP                                                  
***

by **NicC** » Fri Apr 28, 2017 6:22 pm

It looks as though each time you log on the xmit tries again. Fiox the space problem, allow the xmit to complete properly and that is it.

by **Aki88** » Fri Apr 28, 2017 8:24 pm

Hello,

Am not an expert at this, so apologies for incorrect usage of terminology.

From the display shown, it appears that you were not logged out after the B37, meaning a successful logon did happen (my assumption); is it possible for you to delete/define the dataset in question with larger space, because the dataset names are visible in the display, and a B37 can be fixed by tweaking the DS space - provided the DS is not being del/def already within the startup REXX/MACRO/CLIST in which case you'll have to modify the code?
Having said that, if XMIT is not required (and I am not totally sure here why it is needed at all), can you suppress it? To remove the same, you can look at the startup REXX/MACRO/CLIST that is being executed at the time of logon; and tweak it to not execute XMIT at all during the next logon.

Hope this helps.

by **Pedro** » Fri Apr 28, 2017 9:43 pm

What I can tell from the messages:

1. you previously sent a data set to someone else (maybe to yourself on a different system).
2. that person has received the data set.
3. you were sent an acknowledgement message that the data set was received.
4. when you login, the system automatically issues a RECEIVE command.
5. the acknowledgement message gets logged to your ATXFOGG.LOG.MISC data set
6. the size of your log file increases and tries to get a new extent, but the dasd is full and the acknowledgement cannot actually be logged to ATXFOGG.LOG.MISC
7. the acknowledgement message stays on the spool.
8. you now live a 'ground hog day' whenever you logon, repeating steps 4-7

Possible solutions:
- free up space on DASD
- rename the old log data set if you want to keep it... the system should create a new one. Otherwise, delete the log data set.
- issue RECEIVE LOGDATASET(my.new.log) to direct the message to a different log data set

by **willy jensen** » Sat Apr 29, 2017 3:47 pm

To answer the general question 'delete messages while I login TSO' -
most installations have a CLEAR-SCREEN command that you can run as part of the login script (REXX or CLIST), to avoid having to press ENTER before ISPF starts up. It of course means that someone have to modify the login script. If you don't have a clear screen command, then there are many sample to be found on the net.

by **steve-myers** » Sat Apr 29, 2017 5:42 pm

willy jensen wrote:To answer the general question 'delete messages while I login TSO' -
most installations have a CLEAR-SCREEN command that you can run as part of the login script (REXX or CLIST), to avoid having to press ENTER before ISPF starts up. It of course means that someone have to modify the login script. If you don't have a clear screen command, then there are many sample to be found on the net.

Willy (and everyone) - Everyone has a tiny program called ISPCLEAR. It's name implies it is part of ISPF, but it can be called as an ordinary program. It's probably in the ISPLLIB data set, and it may be in your link list. ISPCLEAR unconditionally clears the TSO terminal screen. ISPCLEAR has been reverse engineered countless times; as Mr. Jensen says I'm sure you can find it on the internet if you cannot find it in your system.

by **prino** » Sat Apr 29, 2017 6:02 pm

The "standard" was written by Doug Nadel, IBM's (sadly retired) ISPF guru:

Select all

ISPCLEAR CSECT    ,                 ISPF aware clear screen module
ISPCLEAR AMODE    31
ISPCLEAR RMODE    24
         STM      14,12,12(13)
         LR       12,15
         USING    ISPCLEAR,12
         LA       15,SAVEAREA
         ST       15,8(13)
         ST       13,4(15)
         LR       13,15
         STFSMODE INITIAL=YES       Initialize full screen mode
         TPUT     CLR,L'CLR,FULLSCR,,HOLD   Clear the screen
         STLINENO LINE=1            Clear screen & set cursor to line 1
         STFSMODE OFF               Go back to line mode
         STTMPMD  OFF               Let session manager play with us
         TCLEARQ  INPUT             Clear input queue
         L        15,=V(ISPQRY)     Load ISPF environment test address
         BALR     14,15             See if ISPF is available
         LTR      15,15
         BNZ      NOISPF            If not, go to exit
         L        15,=V(ISPLINK)    Load ISPLINK interface address
         LA       1,ISPPARMS        ISPLINK CONTROL DISPLAY REFRESH
         BALR     14,15             To force screen refresh on return
NOISPF   L        13,4(13)
         LM       14,12,12(13)
         XR       15,15             Always return a zero return code
         BR       14
SAVEAREA DS       9D
ISPPARMS DC       A(CONTROL),A(DISPLAY),A(REFRESH+X'80000000')
CONTROL  DC       CL8'CONTROL '
DISPLAY  DC       CL8'DISPLAY '
REFRESH  DC       CL8'REFRESH '
CLR      DC       X'401140403C40400013'
         DS       0F
         LTORG
         END      ISPCLEAR

IBM Mainframe Forum

How to delete messages in Login Spool

How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool

Re: How to delete messages in Login Spool