[Library] [Contents] [Revisions] [Prev Topic] [Next Topic] [Search] [Search Results] [Prev Topic Match] [Next Topic Match] [Notes] [List Notes] [Print] [Download] [Help]

1.3.6 Storing Transmitted Data in a Log



A LOG data set is a journal of all TRANSMIT and RECEIVE activity. It keeps a record of:



    ___ Example of a LOG data set __________________________________________  
   |   TRANSMIT         ** MESSAGE **              16 SEP 1987 10:26:16     | 
   |     TO: TOM        NODEID   TJONES  Tom Jones                          | 
   |   This is the text of a message that was                               | 
   |   transmitted                                                          | 
   |   ---------------------------------------------------------------------| 
   |   RECEIVE          ** ACKNOWLEDGMENT **       16 SEP 1987 10:34:06     | 
   |    FROM: TOM       NODEID  TJONES Tom Jones   16 SEP 1987 10:34:06     | 
   |      STORED        ** MESSAGE **              16 SEP 1987 10:26:16     | 
   |   ---------------------------------------------------------------------| 
   |   RECEIVE          A.SEQ.DATA                 17 SEP 1987 11:34:06     | 
   |    FROM: TOM       NODEID JONES Tom Jones     17 SEP 1987 11:30:10     | 
   |   This is the text of a message that was                               | 
   |   received along with a data set (SEQ.DATA)                            | 
   |       DSN:  YOURID.SEQ.DATA                                            | 
   |                                                                        | 
   |________________________________________________________________________| 


   The three entries in the above LOG data set show: 




   You may have several LOG data sets or just one. The default data set name 
   is usually PREFIX.LOG.MISC but you can specify another name with the 
   :LOGSEL and :LOGNAME tags in your Names data set. The :LOGSEL tag changes 
   the second data set qualifier and the :LOGNAME tag changes the third data 
   set qualifier.  For more information about these tags see "Using Nicknames 
   and the Names Data Set" in topic 1.3.4. 


   Another way to direct information to a specific log when sending 
   information is with the LOGNAME operand of the TRANSMIT command. The 
   LOGNAME operand changes the third data set qualifier. For more information 
   about this operand, see OS/390 TSO/E Command Reference. 


   In addition, you can specify a log name with the LOGDATASET (or LOGDSNAME) 
   operand on either or both of the RECEIVE and TRANSMIT commands. If the log 
   data set does not exist, a sequential data set is created. If the log data 
   set already exists and it is not sequential, you see an error message. 
   This log name operand allows you to keep a log of transmissions. 


   If your installation uses security labels and security checking, the 
   security label you are logged on at is associated with the transmitted 
   data. 


    ___ Example ____________________________________________________________  
   | To receive records of transmitted data to a log data set named         | 
   | PREFIX.MY.TRASH, enter:                                                | 
   |                                                                        | 
   |   RECEIVE LOGDATASET(my.trash)                                         | 
   |                                                                        | 
   |________________________________________________________________________| 


   When you specify more than one log data set, certain operands override 
   others. The possibilities are as follows beginning with the most general. 
   Each successive possibility overrides the previous one. 




   The LOG/NOLOG tags and operands of the TRANSMIT command have a similar 
   precedence. When the tags are used in the control section of your Names 
   data set, they can be overridden when they are used with a specific 
   nickname. The LOG/NOLOG operand of the TRANSMIT command overrides all 
   previous specifications. 


   For more information about these operands, see OS/390 TSO/E Command 
   Reference. 



[Prev Topic] [Next Topic] © Copyright IBM Corp. 1988, 2000

IBM BookManager® BookServer Copyright 1989, 1999 IBM Corporation. All rights reserved.


Return to library: [ OS/390 | TPF | VM | VSE | IBM Hardware | S/390 Redbooks | RS/6000 SP ]

Glossary - IBM Dictionary of Computing

How to: [ Order publications | Contact OS/390 ]