8. EMERGENGIA Y CONSOLIDACION PROGRESIVA DEL EQUIPAI4IENTO EScOLAR INFANTIL
8.1. SITUACION ESCOLAR DE LA PRIMERA INFANCIA EN EL MUNICIPIO DE MOARA
Storing Transmitted Data in a Log
A LOG data set is a journal of all TRANSMIT and RECEIVE activity. It keeps a record of:
What you transmitted
To whom you transmitted
When you transmitted
When what you transmitted was received (acknowledgment)
What you received
From whom you received
When you received
Example of a LOG data set
TRANSMIT \\ MESSAGE \\ 16 SEP 1987 1ð:26:16 TO: TOM NODEID TJONES Tom Jones
This is the text of a message that was transmitted
---RECEIVE \\ ACKNOWLEDGMENT \\ 16 SEP 1987 1ð:34:ð6 FROM: TOM NODEID TJONES Tom Jones 16 SEP 1987 1ð:34:ð6 STORED \\ MESSAGE \\ 16 SEP 1987 1ð:26:16
---RECEIVE A.SEQ.DATA 17 SEP 1987 11:34:ð6
FROM: TOM NODEID JONES Tom Jones 17 SEP 1987 11:3ð:1ð 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:
A transmitted message
Acknowledgment that a message you sent was received
A message received along with a data set.
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” on page 3-8.
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.
Storing Transmitted Data in a Log
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.
No operands - Information goes to PREFIX.LOG.MISC (or whatever default log data set your installation has set up.)
:LOGSEL and :LOGNAME tags in the control section of your Names data set -Information to and from addressees in the Names data set goes to the
specified log data set name whose second and third qualifiers override LOG.MISC.
:LOGNAME tag in the nickname section of your Names data set - Information to and from a particular addressee in the Names data set goes to the specified log data set name whose third qualifier overrides both the 'MISC' in LOG.MISC and the third qualifier specified with the :LOGNAME tag in the control section of your Names data set.
LOGNAME operand of the TRANSMIT command - Information sent to a particular person is recorded in a log data set whose third qualifier is specified with the LOGNAME operand.
LOGDATASET (or LOGDSNAME) operand of the RECEIVE command -Information received is recorded in the log data set specified by the LOGDATASET operand.
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.
Storing Transmitted Data in a Log
Part 2. Using Data Sets
Data sets, as mentioned earlier, are files or units of information. By issuing TSO/E commands, you can manage data sets in the following ways:
Create data sets and specify access to them (ALLOCATE)
Free data sets from your terminal session (FREE)
List data set names and information about data sets (LISTALC, LISTCAT, and LISTDS)
Edit data sets (EDIT)
Rename data sets (RENAME)
Copy the data from one data set to another (SMCOPY)
Send and receive data sets (TRANSMIT, RECEIVE)
Print data sets (PRINTDS)
Delete data sets from the system (DELETE).
This part contains the following chapters:
Chapter 4, “Allocating Data Sets” on page 4-1 describes allocation and how to use the ALLOCATE command to access data sets for input and output.
Chapter 5, “Releasing Data Sets” on page 5-1 describes the FREE command and ways you can release allocated data sets.
Chapter 6, “Listing Data Set Information” on page 6-1 describes three commands that list information about data sets. The LISTALC command lists the names and information about data sets currently allocated to your terminal session; the LISTCAT command lists the names and information about data sets that begin with your prefix; the LISTDS command lists information about specific data sets.
Chapter 7, “Editing Data Sets” on page 7-1 describes the TSO/E editing facilities. You can edit data sets using the line mode editor associated with the EDIT command, or you can use the full-screen editor with ISPF/PDF. This chapter briefly describes both methods.
Chapter 8, “Renaming Data Sets” on page 8-1 explains the RENAME command and how you can rename a data set.
Chapter 9, “Copying Data Sets” on page 9-1 explains how you can copy one data set to another using the SMCOPY command.
Chapter 10, “Sending and Receiving Data Sets” on page 10-1 explains how you can send and receive data sets. To send longer messages and data sets, use the TRANSMIT command. To receive longer messages and data sets, use the RECEIVE command.
Chapter 11, “Printing Data Sets” on page 11-1 describes the PRINTDS command and gives examples of the many options for printing and formatting data sets.
Chapter 12, “Deleting Data Sets” on page 12-1 describes how you can use the DELETE command to delete data sets from a particular volume or from the catalog.