Re: *DTS data in msgdta

Which format should I select as the output, or, is this not what I want?
Output format
    INPUT; CHAR(10)
 
    The format to convert the data to.  Valid values are:
 
    *DTS        System time-stamp.  For additional information, see the 
description of the *DTS value under the input format parameter.
    *JOB        The format given in the DATFMT job attribute
    *SYSVAL     The format given in the QDATFMT system value
    *YMD        YYMMDD format
    *YYMD       YYYYMMDD format
    *MDY        MMDDYY format
    *MDYY       MMDDYYYY format
    *DMY        DDMMYY format
    *DMYY       DDMMYYYY format
    *JUL        Julian format (YYDDD)
    *LONGJUL    Long Julian format (YYYYDDD)
    *DOS        DOSGetDateTime format.  The *DOS value can be specified only 
when *CURRENT or *DTS is specified for the input format 
                parameter.




bvining@VNET.IBM.COM on 10/30/98 01:52:06 PM
Please respond to MIDRANGE-L@midrange.com@Internet
To:     MIDRANGE-L@midrange.com@Internet
cc:      

Subject:        *DTS data in msgdta

Use the Convert Date and Time Format (QWCCVTDT) API documented in the
Miscellaneous chapter of the System API Reference.  *DTS is one of the
supported formats.

Bruce Vining

>
>I am doing a RCVMSG monitoring a message queue.  Currently the
>most important message is CPI8050.  When a do a DSPMSGD on CPI8050
>it has the following data fields:
>Field     Data Type     Length
> &1       *CHAR             8
> &2       *CHAR             8
> &3       *CHAR             8
> &4       *CHAR             8
> &5       *CHAR            10
> &6       *CHAR            10
> &7       *CHAR             6
> &8       *DTS
> &9       *DTS
> &10      *BIN              4
> &11      *CHAR             7
>
>I've discovered that &8 and &9 take up 8 positions each in the
>msgdta.  I do the following in my CL:
>/*
> | SENTTIME & RCVDTIME are both stored funky and I haven't been
> | able to figure them out.
>*/
>         CHGVAR     VAR(&SENTTIME) VALUE(%SST(&MSGDTA 59  8))
>         CHGVAR     VAR(&RCVDTIME) VALUE(%SST(&MSGDTA 67  8))
>How do I convert the above into human readable?
>I've tried breaking up &SENTTIME into four 2 character binary fields
>and two 4 character binary fields, and doing
>CHGVAR     VAR(&NUMERIC) VALUE(%BINARY(&BIN4))   or &BIN2
>and none of the chunks made sense.
>
>The way to generate CPI8050 is to do a SNDNETF.
>
>The CL programming guide has the following about using *DTS in message
>descriptions:
>
>The following data types are valid only in IBM-supplied message
>descriptions and should not be used for other messages:
>
>:   Time interval (*ITV).  An 8-byte time interval that contains the
>    time to the nearest whole second for various wait time out conditions.
>
>:   Date and time stamp (*DTS).  An 8-byte system date and time stamp for
>    which the date is to be formatted as specified in the QDATFMT and
>    QDATSEP system values and the time is to be formatted as hh:mm:ss.
>

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---