<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Incorrect packed decimal values in SAS Programming</title>
    <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606873#M176304</link>
    <description>&lt;P&gt;Please show the lines from the log for the example tests that I asked you to run.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If something is messing up the binary data and not the text data then your run that prints the data as text instead of binary strings will not be impacted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here is another test.&amp;nbsp; Write the data to a file using PD8.6 format and then read it back in immediately in the same job.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also what JCL (or whatever the modern equivalent) are you using to define the output file your data step is creating? Perhaps there is some setting that that is messing up the binary strings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Nov 2019 04:24:59 GMT</pubDate>
    <dc:creator>Tom</dc:creator>
    <dc:date>2019-11-25T04:24:59Z</dc:date>
    <item>
      <title>Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606549#M176143</link>
      <description>&lt;P&gt;I am running a SAS (version 9.4) report on the mainframe (z/OS 2.3) and receiving incorrect packed decimal values in my output.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The report is using MXG to process CICS 110 SMF records.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the code for the report with the fields as edited numerics (16.6). The fields in question are ELAPSEC and CPUSEC&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;OPTIONS SOURCE;                                                     
%VMXGSUM(                                                           
   INDATA=PDB.CICSTRAN (KEEP=SMFTIME   APPLID   TRANNAME CPUTM      
                             ELAPSTM   SASDDATE  SMFDT            );
   FORMAT SMFDT     $10.;                                           
   FORMAT SASDATE   DATETIME25.6;                                   
   FORMAT ELAPSEC   &lt;STRONG&gt;16.6&lt;/STRONG&gt;;                                           
   FORMAT CPUSEC    &lt;STRONG&gt;16.6&lt;/STRONG&gt;;                                           
                                                                    
   ELAPSEC = ELAPSTM;                                               
   CPUSEC  = CPUTM;                                                 
                                                                    
   SASDATE  = SMFTIME;                                              
   SMFDT    = PUT(DATEPART(SASDATE),YYMMDD10.);,                    
                                                                    
   OUTDATA=CICS,                                                    
   SUMBY=SMFDT APPLID TRANNAME,                                     
   SUM=CPUSEC ELAPSEC,    /* SUMS */                                
   FREQ=NUMTRANS,             /* COUNT THE NUMBER OF JOBS */        
   INCODE=                                                          
     IF TRANNAME NOT IN:('AFC');,
   OUTCODE=                                           
     LABEL NUMTRANS='NUMBER*OF*TRANSACTIONS';         
 );                                                  
PROC REPORT DATA=CICS NOWD NOHEADER LS=80;           
OPTIONS NODATE NONUMBER;                             
TITLE1; TITLE2;                                      
COLUMN SMFDT APPLID TRANNAME NUMTRANS CPUSEC ELAPSEC;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Here is the output with edited numerics. This output is correct.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;2019-11-20  A70AL001  ADGK        220          0.232033         75.437365
2019-11-20  A70AL001  ADGS       2768          2.782727        810.000074
2019-11-20  A70AL001  DAMY          1          0.001483          0.001914
2019-11-20  A70AL001  IALG       2406         12.758015       8407.511169
2019-11-20  A70AL001  IALK        188          1.040738        618.207749
2019-11-20  A70AL002  ADGS        343          0.299851         29.035216
2019-11-20  A70AL002  DCRY          1          0.000220          0.000558
2019-11-20  A70AL002  IALG        312          1.930452        234.981871&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;Next, I ran the report with ELAPSEC and CPUSEC as packed decimal (PD8.6).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;OPTIONS SOURCE;                                                     
%VMXGSUM(                                                           
   INDATA=PDB.CICSTRAN (KEEP=SMFTIME   APPLID   TRANNAME CPUTM      
                             ELAPSTM   SASDDATE  SMFDT            );
   FORMAT SMFDT     $10.;                                           
   FORMAT SASDATE   DATETIME25.6;                                   
   FORMAT ELAPSEC   &lt;STRONG&gt;PD8.6&lt;/STRONG&gt;;                                           
   FORMAT CPUSEC    &lt;STRONG&gt;PD8.6&lt;/STRONG&gt;;                                           
                                                                    
   ELAPSEC = ELAPSTM;                                               
   CPUSEC  = CPUTM;                                                 
                                                                    
   SASDATE  = SMFTIME;                                              
   SMFDT    = PUT(DATEPART(SASDATE),YYMMDD10.);,                    
                                                                    
   OUTDATA=CICS,                                                    
   SUMBY=SMFDT APPLID TRANNAME,                                     
   SUM=CPUSEC ELAPSEC,    /* SUMS */                                
   FREQ=NUMTRANS,             /* COUNT THE NUMBER OF JOBS */        
   INCODE=                                                          
     IF TRANNAME NOT IN:('AFC');,
   OUTCODE=                                           
     LABEL NUMTRANS='NUMBER*OF*TRANSACTIONS';         
 );                                                  
PROC REPORT DATA=CICS NOWD NOHEADER LS=80;           
OPTIONS NODATE NONUMBER;                             
TITLE1; TITLE2;                                      
COLUMN SMFDT APPLID TRANNAME NUMTRANS CPUSEC ELAPSEC;&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is the output. I turned HEX ON to see the associated hex values for each byte. There are non numerics within the packed decimal nibbles.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, some of the packed decimal values close (an 8 transposed as a C), but others are wildly inaccurate. The second packed field for A70AL002 DCRY should be 00000000000558C. Instead, it is&amp;nbsp;0000000000075AC.&lt;/P&gt;&lt;DIV class="postDiv"&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;2019-11-20  A70AL001  ADGK        220                È  *
FFFF6FF6FF44CFFCDFFF44CCCD44444444FFF44000003034400007335
2019011020001701300100147200000000220000000223C000007476C
---------------------------------------------------------
2019-11-20  A70AL001  ADGS       2768       BÊ@     A   &amp;lt;
FFFF6FF6FF44CFFCDFFF44CCCE4444444FFFF4400002&lt;STRONG&gt;C&lt;/STRONG&gt;7744000&lt;STRONG&gt;C&lt;/STRONG&gt;0004
2019011020001701300100147200000002768000000722C000001007C
---------------------------------------------------------
2019-11-20  A70AL001  DAMY          1        Ç         J&amp;lt;
FFFF6FF6FF44CFFCDFFF44CCDE4444444444F440000006344000000&lt;STRONG&gt;D&lt;/STRONG&gt;4
2019011020001701300100414800000000001000000018C000000011C
---------------------------------------------------------
2019-11-20  A70AL001  IALG       2406       Ì *      Í  Æ
FFFF6FF6FF44CFFCDFFF44CCDC4444444FFFF44000027054400047119
2019011020001701300100913700000002406000001781C000080516E
---------------------------------------------------------
2019-11-20  A70AL001  IALK        188        ËÐ     /B ÈÆ
FFFF6FF6FF44CFFCDFFF44CCDD44444444FFF440000147&lt;STRONG&gt;A&lt;/STRONG&gt;440006&lt;STRONG&gt;C&lt;/STRONG&gt;079
2019011020001701300100913200000000188000000003C000001274E
---------------------------------------------------------
2019-11-20  A70AL002  ADGS        343       RE       °  %
FFFF6FF6FF44CFFCDFFF44CCCE44444444FFF4400000&lt;STRONG&gt;DC&lt;/STRONG&gt;14400009326
2019011020001701300200147200000000343000000295C000002051C&lt;BR /&gt;---------------------------------------------------------
2019-11-20  A70AL002  DCRY          1                  ÍÐ
FFFF6FF6FF44CFFCDFFF44CCDE4444444444F4400000020440000007&lt;STRONG&gt;A&lt;/STRONG&gt;
2019011020001701300200439800000000001000000002C000000005C
---------------------------------------------------------
2019-11-20  A70AL002  IALG        312        Á       ÑAG 
FFFF6FF6FF44CFFCDFFF44CCDC44444444FFF44000013624400026&lt;STRONG&gt;CC&lt;/STRONG&gt;1
2019011020001701300200913700000000312000000905C000003917C&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;/DIV&gt;</description>
      <pubDate>Fri, 22 Nov 2019 21:01:23 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606549#M176143</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-22T21:01:23Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606575#M176149</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/300812"&gt;@BrianChapman&lt;/a&gt;:&lt;/P&gt;
&lt;P&gt;If were trying to track it down, I'd start with comparing the exact actual content of a SAS variable as stored using HEX16. with the value you expect because it is displayed this way by the 16.6 format. For example, if the expected value is 0.000558, I'd print it as:&lt;/P&gt;
&lt;PRE&gt;data _null_ ;                                                                                                                                                                                                                                                   
  v = 0.000558 ;                                                                                                                                                                                                                                                
  put v = hex16. ;                                                                                                                                                                                                                                              
run ; 
&lt;/PRE&gt;
&lt;P&gt;On my system it prints as v=3F4248D7E02645E5, but of course on yours (i.e. z/OS) it is different. Make a note of it. Then print ELAPSEC using HEX16. from the record where you have 0.000558 as printed by 16.6. Is the HEX16. value of ELAPSEC the same as printed by the DATA step above? &amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Kind regards&lt;/P&gt;
&lt;P&gt;Paul D.&lt;/P&gt;
&lt;P&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 22 Nov 2019 21:18:34 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606575#M176149</guid>
      <dc:creator>hashman</dc:creator>
      <dc:date>2019-11-22T21:18:34Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606679#M176201</link>
      <description>&lt;P&gt;Hashman,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I ran the code provided and here is the output:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;1           DATA _NULL_ ;     
2             V = 0.000558 ;  
3             PUT V = HEX16. ;
4           RUN ;             
                              
V=3E2491AFC04C8BC9            &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;After that, I changed my report and made the output fields "HEX16."&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Here is that output:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;2019-11-20  A70AL001  ADGK        220  403B6689A7000000  424B6FF726000000
2019-11-20  A70AL001  ADGS       2768  412C860CC7000000  4332A0004E000000
2019-11-20  A70AL001  DAMY          1  3E6129D1F6000000  3E7D700000000000
2019-11-20  A70AL001  IALG       2406  41CC20D449000000  4420D782DC000000
2019-11-20  A70AL001  IALK        188  4110A6DCF5000000  4326A352F1000000
2019-11-20  A70AL002  ADGS        343  404CC30D86000000  421D0903ED000000
2019-11-20  A70AL002  DCRY          1  3DE6842741000000  3E24910000000000
2019-11-20  A70AL002  IALG        312  411EE321A5000000  42EAFB5BE8000000&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;I see that the first 3 bytes are the same '3E2491'.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 14:49:26 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606679#M176201</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-23T14:49:26Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606691#M176211</link>
      <description>&lt;P&gt;At least when running SAS on windows there is difference in the output of PD and S370FPD formats.&lt;/P&gt;
&lt;PRE&gt;159   data test;
160     x= 0.000558;
161     y=put(x,pd8.6);
162     z=put(x,s370Fpd8.6);
163     put x 16.6 / y $hex16. / z $hex16. ;
164   run;

        0.000558
0000000000000558
000000000000558C
&lt;/PRE&gt;
&lt;P&gt;Why does there appear to be a call to PROC REPORT in the middle of your code?&amp;nbsp; It doesn't make much sense to generated packed decimal strings into a report. They are BINARY strings.&amp;nbsp; Normally to write them to a data file you would just use a data step and a PUT statement.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 17:45:51 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606691#M176211</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-11-23T17:45:51Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606700#M176216</link>
      <description>&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I changed it to output the data using the DATA and PUT statements.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;  OPTIONS SOURCE;                                                      
  %VMXGSUM(                                                            
     INDATA=PDB.CICSTRAN (KEEP=SMFTIME   APPLID   TRANNAME CPUTM       
                               ELAPSTM                                 
                               SASDDATE  SMFDT    CPUSEC            ); 
     FORMAT SMFDT     $10.;                                            
     FORMAT SASDATE   DATETIME25.6;                                    
     FORMAT ELAPSEC   16.6;                                            
     FORMAT CPUSEC    16.6;                                            
                                                                       
     ELAPSEC = ELAPSTM;                                                
     CPUSEC  = CPUTM;                                                  
                                                                       
     SASDATE  = SMFTIME;                                               
     SMFDT    = PUT(DATEPART(SASDATE),YYMMDD10.);,                     
                                                                       
     OUTDATA=CICS,                                                     
     SUMBY=SMFDT APPLID TRANNAME,                                      
     SUM=CPUSEC ELAPSEC,    /* SUMS */                                 
     FREQ=NUMTRANS,         /* COUNT THE NUMBER OF TRANSACTIONS */             
     INCODE=                                                           
        IF TRANNAME NOT IN:('AFC');,
     OUTCODE=                                                          
       LABEL NUMTRANS='NUMBER*OF*TRANSACTIONS';                        
    );                                                                 
   DATA _NULL_; SET CICS;                                              
   FILE SASLIST;                                                       
                                                                       
   PUT @001 SMFDT       $10.     /* JOBNAME                          */
       @012 APPLID      $8.      /* VTAM APPLICATION NAME            */
       @022 TRANNAME    $4.      /* TRANSACTION ID                   */
       @028 NUMTRANS     8.      /* NUMBER OF TRANSACTIONS           */
       @038 CPUSEC      PD8.6    /* CPU SECONDS                      */
       @048 ELAPSEC     PD8.6;   /* ELAPSED SECONDS                  */
   RUN;                                                                &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;I still get invalid packed values.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;2019-11-20 A70AL001  ADGK       220                È  *
FFFF6FF6FF4CFFCDFFF44CCCD4444444FFF44000003034400007335
20190110200170130010014720000000220000000223C000007476C
-------------------------------------------------------
2019-11-20 A70AL001  ADGS      2768       BÊ@     A   &amp;lt;
FFFF6FF6FF4CFFCDFFF44CCCE444444FFFF4400002C7744000C0004
20190110200170130010014720000002768000000722C000001007C
-------------------------------------------------------
2019-11-20 A70AL001  DAMY         1        Ç         J&amp;lt;
FFFF6FF6FF4CFFCDFFF44CCDE444444444F440000006344000000D4
20190110200170130010041480000000001000000018C000000011C
-------------------------------------------------------
2019-11-20 A70AL001  IALG      2406       Ì *      Í  Æ
FFFF6FF6FF4CFFCDFFF44CCDC444444FFFF44000027054400047119
20190110200170130010091370000002406000001781C000080516E
-------------------------------------------------------
2019-11-20 A70AL001  IALK       188        ËÐ     /B ÈÆ
FFFF6FF6FF4CFFCDFFF44CCDD4444444FFF440000147A440006C079
20190110200170130010091320000000188000000003C000001274E
-------------------------------------------------------
2019-11-20 A70AL002  ADGS       343       RE       °  %
FFFF6FF6FF4CFFCDFFF44CCCE4444444FFF4400000DC14400009326
20190110200170130020014720000000343000000295C000002051C
-------------------------------------------------------
2019-11-20 A70AL002  DCRY         1                  ÍÐ
FFFF6FF6FF4CFFCDFFF44CCDE444444444F4400000020440000007A
20190110200170130020043980000000001000000002C000000005C
-------------------------------------------------------
2019-11-20 A70AL002  IALG       312        Á       ÑAG 
FFFF6FF6FF4CFFCDFFF44CCDC4444444FFF44000013624400026CC1
20190110200170130020091370000000312000000905C000003917C&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 19:05:54 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606700#M176216</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-23T19:05:54Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606705#M176220</link>
      <description>&lt;P&gt;I also changed the output format to S370FPD, and I still got the same output.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE class=" language-sas"&gt;&lt;CODE class="  language-sas"&gt;   &lt;SPAN class="token keyword"&gt;PUT&lt;/SPAN&gt; &lt;SPAN class="token punctuation"&gt;@&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;001&lt;/SPAN&gt; SMFDT       &lt;SPAN class="token punctuation"&gt;$&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;10&lt;/SPAN&gt;&lt;SPAN class="token punctuation"&gt;.&lt;/SPAN&gt;        &lt;SPAN class="token comment"&gt;/* JOBNAME                      */&lt;/SPAN&gt;
       &lt;SPAN class="token punctuation"&gt;@&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;012&lt;/SPAN&gt; APPLID      &lt;SPAN class="token punctuation"&gt;$&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;8&lt;/SPAN&gt;&lt;SPAN class="token punctuation"&gt;.&lt;/SPAN&gt;         &lt;SPAN class="token comment"&gt;/* VTAM APPLICATION NAME        */&lt;/SPAN&gt;
       &lt;SPAN class="token punctuation"&gt;@&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;022&lt;/SPAN&gt; TRANNAME    &lt;SPAN class="token punctuation"&gt;$&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;4&lt;/SPAN&gt;&lt;SPAN class="token punctuation"&gt;.&lt;/SPAN&gt;         &lt;SPAN class="token comment"&gt;/* TRANSACTION ID               */&lt;/SPAN&gt;
       &lt;SPAN class="token punctuation"&gt;@&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;028&lt;/SPAN&gt; NUMTRANS     &lt;SPAN class="token number"&gt;8&lt;/SPAN&gt;&lt;SPAN class="token punctuation"&gt;.&lt;/SPAN&gt;         &lt;SPAN class="token comment"&gt;/* NUMBER OF TRANSACTIONS       */&lt;/SPAN&gt;
       &lt;SPAN class="token punctuation"&gt;@&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;038&lt;/SPAN&gt; CPUSEC      S370FPD8&lt;SPAN class="token punctuation"&gt;.&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;6&lt;/SPAN&gt;  &lt;SPAN class="token comment"&gt;/* CPU SECONDS                  */&lt;/SPAN&gt;
       &lt;SPAN class="token punctuation"&gt;@&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;048&lt;/SPAN&gt; ELAPSEC     S370FPD8&lt;SPAN class="token punctuation"&gt;.&lt;/SPAN&gt;&lt;SPAN class="token number"&gt;6&lt;/SPAN&gt;&lt;SPAN class="token punctuation"&gt;; &lt;/SPAN&gt;&lt;SPAN class="token comment"&gt;/* ELAPSED SECONDS              */&lt;/SPAN&gt;
   &lt;SPAN class="token procnames"&gt;RUN&lt;/SPAN&gt;&lt;SPAN class="token punctuation"&gt;;&lt;/SPAN&gt;  &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 19:49:32 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606705#M176220</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-23T19:49:32Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606706#M176221</link>
      <description>&lt;P&gt;Why do you think the value is wrong?&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Output looks fine to me.&lt;/P&gt;
&lt;PRE&gt;206   /*
207   2019-11-20 A70AL001  ADGK       220                È  *
208   ----+---10----+---20----+---30----+---40----+---50----+----0
209   FFFF6FF6FF4CFFCDFFF44CCCD4444444FFF44000003034400007335
210   20190110200170130010014720000000220000000223C000007476C
211   */
212
213   data test;
214     hexstr='000000077437365C'x;
215     format hexstr $hex16.;
216     x  = input(hexstr,s370fpd8.6);
217     put (_all_) (=);
218   run;

hexstr=000000077437365C x=77.437365
NOTE: The data set WORK.TEST has 1 observations and 2 variables.
&lt;/PRE&gt;
&lt;P&gt;Certainly looks like what the SAS doucmentaion says that PD format generates when running on Z/OS.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://documentation.sas.com/?docsetId=hosto390&amp;amp;docsetTarget=n1shzbsiufgrzin1f3q38pdsfpw7.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en"&gt;https://documentation.sas.com/?docsetId=hosto390&amp;amp;docsetTarget=n1shzbsiufgrzin1f3q38pdsfpw7.htm&amp;amp;docsetVersion=9.4&amp;amp;locale=en&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 20:00:42 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606706#M176221</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-11-23T20:00:42Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606708#M176223</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/159"&gt;@Tom&lt;/a&gt;:&lt;/P&gt;
&lt;P&gt;Yes, there is - because you're not running under z/OS.&lt;/P&gt;
&lt;P&gt;On non-z/OS platforms, PDw.d renders the same as PKw.d, i.e. neither places the sign marker in the last nibble, while s370FPDw.d does (C or D,depending on plus or minus), and so does s370FPDUw.d (unsigned, places F in the last nibble).&lt;/P&gt;
&lt;P&gt;On z/OS, PDw.d and s370FPDw.d are exactly the same (they write the sign) but different from PKw.d (it does not).&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 20:09:43 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606708#M176223</guid>
      <dc:creator>hashman</dc:creator>
      <dc:date>2019-11-23T20:09:43Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606709#M176224</link>
      <description>&lt;P&gt;So he either needs to use PK format to write or leave the values as is and use S370FPD informat to read.&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 20:16:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606709#M176224</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-11-23T20:16:58Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606712#M176225</link>
      <description>&lt;P&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/300812"&gt;@BrianChapman&lt;/a&gt;:&lt;/P&gt;
&lt;P&gt;Well, it tells us something, doesn't it? Namely, that the value stored in the SAS variable is not 0.000558 but just 558 (i.e. the time is stored as integer in microseconds). To confirm, run:&lt;/P&gt;
&lt;PRE&gt;DATA _NULL_ ;              
  RETAIN V 0.000558 I 558 ;
  PUT V=HEX16. / I=HEX16. ;
RUN ;                      
&lt;/PRE&gt;
&lt;P&gt;How does this step print I=HEX16. on your system?&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sat, 23 Nov 2019 20:53:38 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606712#M176225</guid>
      <dc:creator>hashman</dc:creator>
      <dc:date>2019-11-23T20:53:38Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606830#M176288</link>
      <description>&lt;P&gt;The value is wrong. 77437365C is a valid packed value, but it's the wrong value for the data. Take a look at my original post. I posted the accurate edited numeric values. It's supposed to be 75437365C.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Also, take a look at the second packed decimal column for the last row (A70AL002 IALG). It's supposed to be 234981871C. Instead it is 2369C1C71C. The third digit is wrong and the '8' digits have been transposed as 'C'. Packed decimal values can only have alphabetic values as the low order digit (typically ending in 'C' or 'D').&lt;/P&gt;</description>
      <pubDate>Sun, 24 Nov 2019 18:55:09 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606830#M176288</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-24T18:55:09Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606832#M176289</link>
      <description>&lt;P&gt;Yes. PD and S370FPD behave the same on z/OS. SAS is generating the numbers in proper form, but the values are wrong.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;77437365C is a valid packed value, but it's the wrong value for the data. It's supposed to be 75437365C.&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 24 Nov 2019 18:58:44 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606832#M176289</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-24T18:58:44Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606834#M176290</link>
      <description>&lt;BLOCKQUOTE&gt;&lt;HR /&gt;&lt;a href="https://communities.sas.com/t5/user/viewprofilepage/user-id/300812"&gt;@BrianChapman&lt;/a&gt;&amp;nbsp;wrote:&lt;BR /&gt;
&lt;P&gt;The value is wrong. 77437365C is a valid packed value, but it's the wrong value for the data. Take a look at my original post. I posted the accurate edited numeric values. It's supposed to be 75437365C.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also, take a look at the second packed decimal column for the last row (A70AL002 IALG). It's supposed to be 234981871C. Instead it is 2369C1C71C. The third digit is wrong and the '8' digits have been transposed as 'C'. Packed decimal values can only have alphabetic values as the low order digit (typically ending in 'C' or 'D').&lt;/P&gt;
&lt;HR /&gt;&lt;/BLOCKQUOTE&gt;
&lt;P&gt;You will need to debug this yourself.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;To start just subset the data to one o the example values that looks wrong and make sure exactly what value the variable has for that observation.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;data _null_;
  SET CICS;
  where SMFDT ='2019-11-20'
    and APPLID= 'A70AL002'
    and TRANNAME ='IALG'
  ;
  test1=put(ELAPSEC,PD8.6);&lt;BR /&gt;  test2=put(ELAPSEC,PK8.6);
  put ELAPSEC / ELAPSEC HEX16. / ELAPSEC 17.6 / ELAPSEC BEST17.6 / test1 $hex16. / test2 $hex16.;
run;&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It the values in the log for TEST1 look like what you want then check and make sure there is not some other process that is modifying the file before you look at it.&amp;nbsp; For example if you are moving that file using something like an FTP process and it is treating it as TEXT instead of BINARY then it will get mangled.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Looking at the values you are talking about here is what I see:&lt;/P&gt;
&lt;PRE&gt;250   data test;
251     do hexstr='000000075437365C'x,'000000077437365C'x,'000000234981871C'x;
252       num = input(hexstr,s370fpd8.6);
253       put hexstr=$hex16. num=17.6 num=best17.6 ;
254     end;
255   run;

hexstr=000000075437365C num=75.437365 num=75.437365
hexstr=000000077437365C num=77.437365 num=77.437365
hexstr=000000234981871C num=234.981871 num=234.981871
&lt;/PRE&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Sun, 24 Nov 2019 20:05:03 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606834#M176290</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-11-24T20:05:03Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606835#M176291</link>
      <description>&lt;P&gt;Note that '8187'x in EBCDIC are the letters 'ag'. While 'C1C7'x in EBCDIC are the letters 'AG'.&lt;/P&gt;
&lt;P&gt;Did something try to UPCASE() the characters in your file?&lt;/P&gt;</description>
      <pubDate>Sun, 24 Nov 2019 20:22:01 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606835#M176291</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-11-24T20:22:01Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606856#M176297</link>
      <description>&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The input data has not been modified.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 00:57:04 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606856#M176297</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-25T00:57:04Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606857#M176298</link>
      <description>&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I can replicate the two scenarios over and over. If I leave the output fields as edited numerics (16.6), then the output is correct. If I change the output fields to packed decimal (PD8.6), then I get the wrong values. The input data has not been modified. There are no other external factors (FTP, another user modifying the data, etc).&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 00:59:58 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606857#M176298</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-25T00:59:58Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606873#M176304</link>
      <description>&lt;P&gt;Please show the lines from the log for the example tests that I asked you to run.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;If something is messing up the binary data and not the text data then your run that prints the data as text instead of binary strings will not be impacted.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Here is another test.&amp;nbsp; Write the data to a file using PD8.6 format and then read it back in immediately in the same job.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Also what JCL (or whatever the modern equivalent) are you using to define the output file your data step is creating? Perhaps there is some setting that that is messing up the binary strings.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 04:24:59 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606873#M176304</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-11-25T04:24:59Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606957#M176343</link>
      <description>&lt;P&gt;Tom,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I tried your test. I also added two extra output lines (format PD8.6 and PK8.6). I think this proves that SAS is not correctly handling the PD and PK output fields.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;  OPTIONS SOURCE;                                                     
  %VMXGSUM(                                                           
     INDATA=PDB.CICSTRAN (KEEP=SMFTIME   APPLID   TRANNAME CPUTM      
                               ELAPSTM                                
                               SASDDATE  SMFDT    CPUSEC            );
     FORMAT SMFDT     $10.;                                           
     FORMAT SASDATE   DATETIME25.6;                                   
     FORMAT ELAPSEC   16.6;                                           
     FORMAT CPUSEC    16.6;                                           
                                                                      
     ELAPSEC = ELAPSTM;                                               
     CPUSEC  = CPUTM;                                                 
                                                                      
     SASDATE  = SMFTIME;                                              
     SMFDT    = PUT(DATEPART(SASDATE),YYMMDD10.);,                    
                                                                      
     OUTDATA=CICS,                                                    
     SUMBY=SMFDT APPLID TRANNAME,                                     
     SUM=CPUSEC ELAPSEC,    /* SUMS */                                
     FREQ=NUMTRANS,         /* COUNT THE NUMBER OF TRANSACTIONS */    
     INCODE=                                                          
        IF  SMFDT    = '2019-11-20'                                   
        AND APPLID   = 'A70AL002'                                     
        AND TRANNAME = 'IALG';,                                       
     OUTCODE=                                                         
       LABEL NUMTRANS='NUMBER*OF*TRANSACTIONS';         
    );                                                  
   DATA _NULL_; SET CICS;                               
   FILE SASLIST;                                        
                                                        
   TEST1=PUT(ELAPSEC,PD8.6);  TEST2=PUT(ELAPSEC,PK8.6); 
   PUT ELAPSEC          /                               
       ELAPSEC HEX16.   /                               
       ELAPSEC 17.6     /                               
       ELAPSEC BEST17.6 /                               
       ELAPSEC PD8.6    /                               
       ELAPSEC PK8.6    /                               
       TEST1   $HEX16.  /                               
       TEST2   $HEX16.;                                   
   RUN;                                                 &lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;The output with HEX ON enabled:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;&amp;nbsp;234.981871       
4FFF4FFFFFF4444444
0234B9818710000000
------------------
 42EAFB5BE8000000 
4FFCCCCFCCFFFFFFF4
042516252580000000
------------------
        234.981871
44444444FFF4FFFFFF
00000000234B981871
------------------
  234.981871128082
44FFF4FFFFFFFFFFFF
00234B981871128082
-----------------
     ÑAG         
400026CC144444444
00003917C00000000
-----------------
      Q É        
400003D1744444444
00002488100000000
-----------------
 000000234981871C
4FFFFFFFFFFFFFFFC
00000002349818713
-----------------
 0000000234981871
4FFFFFFFFFFFFFFFF
00000000234981871&lt;/CODE&gt;&lt;/PRE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 13:41:21 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606957#M176343</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-25T13:41:21Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606958#M176344</link>
      <description>&lt;P&gt;&lt;STRONG&gt;That is not lines from the SAS log. What is HEX ON? What program did you use to generate that output.&amp;nbsp;&lt;/STRONG&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;But it is showing that the PD8.6 is generating the right values.&amp;nbsp; Here is what it printed as the values of TEST2 which had the value of PD8.6 string and you printed using the $HEX16 format so that you could see each nibble of the binary bytes.&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt; 000000234981871C&lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;You can use SAS to show you want is in your file. For example to see what is in the SASLIST file your data step is creating you could use this code:&lt;/P&gt;
&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;DATA _NULL_; 
   INFILE SASLIST;                                        
   input ;
   list;
run;             &lt;/CODE&gt;&lt;/PRE&gt;
&lt;P&gt;Then copy and paste the lines from the SAS LOG.&lt;/P&gt;
&lt;P&gt;You can do the same thing for the file you are creating with the original code.&lt;/P&gt;</description>
      <pubDate>Mon, 25 Nov 2019 13:54:02 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606958#M176344</guid>
      <dc:creator>Tom</dc:creator>
      <dc:date>2019-11-25T13:54:02Z</dc:date>
    </item>
    <item>
      <title>Re: Incorrect packed decimal values</title>
      <link>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606960#M176345</link>
      <description>&lt;P&gt;SASLOG output:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;PRE&gt;&lt;CODE class=" language-sas"&gt;11                                                          THE SAS SYSTEM                            08:28 MONDAY, NOVEMBER 25, 2019
                                                                                                                                     
 NOTE: COPYRIGHT (C) 2002-2012 BY SAS INSTITUTE INC., CARY, NC, USA.                                                                 
 NOTE: SAS (R) PROPRIETARY SOFTWARE 9.4 (TS04.01M2P07232014)                                                                         
       LICENSED TO BLUE CROSS BLUE SHIELD OF SOUTH CAROLINA/MEDICARE, SITE 70011433.                                                 
 NOTE: THIS SESSION IS EXECUTING ON THE Z/OS   V02R03M00 PLATFORM.                                                                   
                                                                                                                                     
 NOTE: RUNNING ON IBM MODEL 3906 SERIAL NUMBER 05A688.                                                                               
                                                                                                                                     
                                                                                                                                     
 NOTE: ADDITIONAL HOST INFORMATION:                                                                                                  
                                                                                                                                     
 IBM 3906-718, SYSF, FMID HBB77B0, CPU: 15, GP: 5, ZAAP: 0, ZIIP: 10                                                                 
                                                                                                                                     
                             WELCOME TO SAS                                                                                          
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 THIS MESSAGE DISPLAYS IN THE SAS LOG WHEN THE NEWS OPTION IS SPECIFIED.                                                             
                                                                                                                                     
 YOU CAN REPLACE IT WITH YOUR OWN MESSAGE BY EDITING THE NEWS FILE.                                                                  
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: THE SASUSER LIBRARY WAS NOT SPECIFIED. SASUSER LIBRARY WILL NOW BE THE SAME AS THE WORK LIBRARY.                              
 NOTE: ALL DATA SETS AND CATALOGS IN THE SASUSER LIBRARY WILL BE DELETED AT THE END OF THE SESSION.  USE THE NOWORKTERM OPTION TO    
       PREVENT THEIR DELETION.                                                                                                       
                                                                                                                                     
 NOTE: SAS SYSTEM OPTIONS SPECIFIED ARE:                                                                                             
       SORT=100                                                                                                                      
                                                                                                                                     
 NOTE: 192M BYTES WERE AVAILABLE ABOVE THE LINE AT INITIALIZATION.                                                                   
                                                                                                                                     
 NOTE: 6208K BYTES WERE AVAILABLE BELOW THE LINE AT INITIALIZATION.                                                                  
                                                                                                                                     
 NOTE: 182M BYTES WERE AVAILABLE ABOVE THE LINE AFTER ADJUSTMENT FOR MEMLEAVE=10M.                                                   
                                                                                                                                     
 NOTE: THE INITIALIZATION PHASE USED 0.02 CPU SECONDS AND 16569K.                                                                    
                                                                                                                                     
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 912K BELOW THE LINE AND 18508K ABOVE THE LINE.                                        
                                                                                                                                     
 WARNING: SAS HAS BEEN STARTED IN NLS COMPATIBILITY MODE WITH THE NLSCOMPATMODE OPTION. THIS OPTION WILL NO LONGER BE SUPPORTED      
          AFTER THIS RELEASE. FOR MORE INFORMATION, CONTACT A SAS REPRESENTATIVE OR TECHNICAL SUPPORT.                               
 NOTE: PROC SQL STATEMENTS ARE EXECUTED IMMEDIATELY; THE RUN STATEMENT HAS NO EFFECT.                                                
                                                                                                                                     
 WELCOME TO MXG SOFTWARE, FROM MERRILL CONSULTANTS, DALLAS, TEXAS                                                                    
 TECH SUPPORT:   214 351 1966    SUPPORT@MXG.COM    WWW.MXG.COM                                                                      
 MXG 37.02 DATED MAR 11, 2019 HAS BEEN INITIALIZED.                                                                                  
                                                                                                                                     
 FILEREF= SOURCLIB                                                                                                                   
 PHYSICAL NAME= SYS19329.T082835.RA000.TS00JY0N.NULLPDS.H06                                                                          
 PHYSICAL NAME= SYS3.MXG.PROD.USERID.SOURCLIB                                                                                        
 PHYSICAL NAME= SYS3.MXG.PROD.SOURCE                                                                                                 
 NOTE: THERE WERE 3 OBSERVATIONS READ FROM THE DATA SET SASHELP.VEXTFL.                                                              
       WHERE UPCASE(FILEREF)='SOURCLIB';                                                                                             
 NOTE: THE DATA STATEMENT USED THE FOLLOWING RESOURCES:                                                                              
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.03                                                                                            
       EXCP COUNT   - 83                                                                                                             
       TASK  MEMORY - 8102K (1662K DATA, 6440K PROGRAM)                                                                              
12                                                          THE SAS SYSTEM                            08:28 MONDAY, NOVEMBER 25, 2019
                                                                                                                                     
       TOTAL MEMORY - 30445K (11040K DATA, 19405K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:28:37 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 912K BELOW THE LINE AND 32832K ABOVE THE LINE.                                        
                                                                                                                                     
                                                                                                                                     
 1            OPTIONS SOURCE;                                                                                                        
 2            %VMXGSUM(                                                                                                              
 MXGNOTE: VMXGSUM LAST UPDATED: CHANGE 36.249, JAN  1, 2018.                                                                         
 3               INDATA=PDB.CICSTRAN (KEEP=SMFTIME   APPLID   TRANNAME CPUTM                                                         
 4                                         ELAPSTM                                                                                   
 5                                         SASDDATE  SMFDT    CPUSEC            );                                                   
 6               FORMAT SMFDT     $10.;                                                                                              
 7               FORMAT SASDATE   DATETIME25.6;                                                                                      
 8               FORMAT ELAPSEC   16.6;                                                                                              
 9               FORMAT CPUSEC    16.6;                                                                                              
 10                                                                                                                                  
 11              ELAPSEC = ELAPSTM;                                                                                                  
 12              CPUSEC  = CPUTM;                                                                                                    
 13                                                                                                                                  
 14              SASDATE  = SMFTIME;                                                                                                 
 15              SMFDT    = PUT(DATEPART(SASDATE),YYMMDD10.);,                                                                       
 16                                                                                                                                  
 17              OUTDATA=CICS,                                                                                                       
 18              SUMBY=SMFDT APPLID TRANNAME,                                                                                        
 19              SUM=CPUSEC ELAPSEC,    /* SUMS */                                                                                   
 20              FREQ=NUMTRANS,         /* COUNT THE NUMBER OF TRANSACTIONS */                                                       
 21              INCODE=                                                                                                             
 22                 IF  SMFDT    = '2019-11-20'                                                                                      
 23                 AND APPLID   = 'A70AL002'                                                                                        
 24                 AND TRANNAME = 'IALG';,                                                                                          
 25              OUTCODE=                                                                                                            
 26                LABEL NUMTRANS='NUMBER*OF*TRANSACTIONS';                                                                          
 27             );                                                                                                                   
 MXGNOTE: VMXGSUM FROM MXG 37.02 HAS BEEN INVOKED                                                                                    
 MXGNOTE: VMXGOPTR LAST UPDATED: SEP 10, 2017. CHANGE 35.194.                                                                        
 MXGNOTE: VGETOBS LAST UPDATED OCT 25, 2018. CHANGE 36.202.                                                                          
                                                                                                                                     
 NOTE: DELETING WORK.OPTVAR (MEMTYPE=DATA).                                                                                          
                                                                                                                                     
                                                                                                                                     
 MXGNOTE: INDATA  = PDB.CICSTRAN (KEEP=SMFTIME APPLID TRANNAME CPUTM ELAPSTM SASDDATE SMFDT CPUSEC ); FORMAT SMFDT $10.; FORMAT      
 SASDATE DATETIME25.6; FORMAT ELAPSEC 16.6; FORMAT CPUSEC 16.6; ELAPSEC=ELAPSTM; CPUSEC=CPUTM; SASDATE=SMFTIME;                      
 SMFDT=PUT(DATEPART(SASDATE),YYMMDD10.);                                                                                             
 MXGNOTE: OUTDATA = CICS                                                                                                             
 MXGNOTE: SUMBY   = SMFDT APPLID TRANNAME                                                                                            
 MXGNOTE: SUMBYCLASS=                                                                                                                
 MXGNOTE: SUM     = CPUSEC ELAPSEC                                                                                                   
 NOTE: THE PROCEDURE DATASETS USED THE FOLLOWING RESOURCES:                                                                          
       CPU     TIME -         00:00:00.18                                                                                            
       ELAPSED TIME -         00:00:00.30                                                                                            
       EXCP COUNT   - 188                                                                                                            
       TASK  MEMORY - 7700K (45K DATA, 7655K PROGRAM)                                                                                
       TOTAL MEMORY - 32057K (10784K DATA, 21273K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:28:37 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 1124K BELOW THE LINE AND 33856K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
13                                                          THE SAS SYSTEM                            08:28 MONDAY, NOVEMBER 25, 2019
                                                                                                                                     
 NOTE: DATA STEP VIEW SAVED ON FILE WORK.MXGSUM1.                                                                                    
 NOTE: A STORED DATA STEP VIEW CANNOT RUN UNDER A DIFFERENT OPERATING SYSTEM.                                                        
 NOTE: THE DATA STATEMENT USED THE FOLLOWING RESOURCES:                                                                              
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.03                                                                                            
       EXCP COUNT   - 61                                                                                                             
       TASK  MEMORY - 4440K (189K DATA, 4251K PROGRAM)                                                                               
       TOTAL MEMORY - 32360K (11040K DATA, 21320K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:28:37 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 1380K BELOW THE LINE AND 33904K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: DELETING WORK.OPTVAR (MEMTYPE=DATA).                                                                                          
 NOTE: THE PROCEDURE DATASETS USED THE FOLLOWING RESOURCES:                                                                          
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.00                                                                                            
       EXCP COUNT   - 4                                                                                                              
       TASK  MEMORY - 4436K (44K DATA, 4392K PROGRAM)                                                                                
       TOTAL MEMORY - 32370K (10784K DATA, 21586K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:28:37 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 1380K BELOW THE LINE AND 34812K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: THE VIEW WORK.MXGSUM1.VIEW USED THE FOLLOWING RESOURCES:                                                                      
       CPU     TIME -         00:00:18.27                                                                                            
       ELAPSED TIME -         00:01:48.24                                                                                            
       EXCP COUNT   - 203412                                                                                                         
       TASK  MEMORY - 4174K (195K DATA, 3979K PROGRAM)                                                                               
       TOTAL MEMORY - 32799K (11168K DATA, 21631K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
 NOTE: THERE WERE 40873952 OBSERVATIONS READ FROM THE DATA SET PDB.CICSTRAN.                                                         
 NOTE: THERE WERE 312 OBSERVATIONS READ FROM THE DATA SET WORK.MXGSUM1.                                                              
 NOTE: THE DATA SET WORK.MXGSUM2 HAS 312 OBSERVATIONS AND 5 VARIABLES.                                                               
 NOTE: COMPRESSING DATA SET WORK.MXGSUM2 INCREASED SIZE BY 100.00 PERCENT.                                                           
       COMPRESSED IS 2 PAGES; UN-COMPRESSED WOULD REQUIRE 1 PAGES.                                                                   
 NOTE: THE PROCEDURE SORT USED THE FOLLOWING RESOURCES:                                                                              
       CPU     TIME -         00:00:18.27                                                                                            
       ELAPSED TIME -         00:01:48.25                                                                                            
       EXCP COUNT   - 41                                                                                                             
       TASK  MEMORY - 4526K (277K DATA, 4249K PROGRAM)                                                                               
       TOTAL MEMORY - 32799K (11168K DATA, 21631K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: DELETING WORK.MXGSUM1 (MEMTYPE=VIEW).                                                                                         
                                                                                                                                     
 NOTE: THE PROCEDURE DATASETS USED THE FOLLOWING RESOURCES:                                                                          
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.00                                                                                            
       EXCP COUNT   - 4                                                                                                              
       TASK  MEMORY - 3934K (44K DATA, 3890K PROGRAM)                                                                                
       TOTAL MEMORY - 32415K (10784K DATA, 21631K PROGRAM)                                                                           
14                                                          THE SAS SYSTEM                            08:30 MONDAY, NOVEMBER 25, 2019
                                                                                                                                     
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: THERE WERE 312 OBSERVATIONS READ FROM THE DATA SET WORK.MXGSUM2.                                                              
 NOTE: THE DATA SET WORK.MXGSUM3 HAS 1 OBSERVATIONS AND 6 VARIABLES.                                                                 
 NOTE: COMPRESSING DATA SET WORK.MXGSUM3 INCREASED SIZE BY 100.00 PERCENT.                                                           
       COMPRESSED IS 2 PAGES; UN-COMPRESSED WOULD REQUIRE 1 PAGES.                                                                   
 NOTE: THE PROCEDURE MEANS USED THE FOLLOWING RESOURCES:                                                                             
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.02                                                                                            
       EXCP COUNT   - 68                                                                                                             
       TASK  MEMORY - 5006K (108K DATA, 4898K PROGRAM)                                                                               
       TOTAL MEMORY - 33148K (10656K DATA, 22492K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: DELETING WORK.MXGSUM2 (MEMTYPE=DATA).                                                                                         
                                                                                                                                     
                                                                                                                                     
 NOTE: THE PROCEDURE DATASETS USED THE FOLLOWING RESOURCES:                                                                          
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.00                                                                                            
       EXCP COUNT   - 4                                                                                                              
       TASK  MEMORY - 4436K (44K DATA, 4392K PROGRAM)                                                                                
       TOTAL MEMORY - 33404K (10912K DATA, 22492K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: THERE WERE 1 OBSERVATIONS READ FROM THE DATA SET WORK.MXGSUM3.                                                                
 NOTE: THE DATA SET WORK.CICS HAS 1 OBSERVATIONS AND 6 VARIABLES.                                                                    
 NOTE: COMPRESSING DATA SET WORK.CICS INCREASED SIZE BY 100.00 PERCENT.                                                              
       COMPRESSED IS 2 PAGES; UN-COMPRESSED WOULD REQUIRE 1 PAGES.                                                                   
 NOTE: THE DATA STATEMENT USED THE FOLLOWING RESOURCES:                                                                              
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.00                                                                                            
       EXCP COUNT   - 7                                                                                                              
       TASK  MEMORY - 5478K (153K DATA, 5325K PROGRAM)                                                                               
       TOTAL MEMORY - 33276K (10784K DATA, 22492K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: DELETING WORK.MXGSUM3 (MEMTYPE=DATA).                                                                                         
 NOTE: THE PROCEDURE DATASETS USED THE FOLLOWING RESOURCES:                                                                          
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.00                                                                                            
       EXCP COUNT   - 4                                                                                                              
       TASK  MEMORY - 4006K (44K DATA, 3962K PROGRAM)                                                                                
       TOTAL MEMORY - 33532K (11040K DATA, 22492K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
15                                                          THE SAS SYSTEM                            08:30 MONDAY, NOVEMBER 25, 2019
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
                                                                                                                                     
 NOTE: DELETING WORK.KEEPERS (MEMTYPE=DATA).                                                                                         
 NOTE: DELETING WORK.KEEPDATA (MEMTYPE=DATA).                                                                                        
 NOTE: DELETING WORK.VAR1 (MEMTYPE=DATA).                                                                                            
                                                                                                                                     
 NOTE: THE PROCEDURE DATASETS USED THE FOLLOWING RESOURCES:                                                                          
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.00                                                                                            
       EXCP COUNT   - 6                                                                                                              
       TASK  MEMORY - 4006K (44K DATA, 3962K PROGRAM)                                                                                
       TOTAL MEMORY - 33532K (11040K DATA, 22492K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
 28            DATA _NULL_; SET CICS;                                                                                                
 29            FILE SASLIST;                                                                                                         
 30                                                                                                                                  
 31            TEST1=PUT(ELAPSEC,PD8.6);  TEST2=PUT(ELAPSEC,PK8.6);                                                                  
 32            PUT ELAPSEC          /                                                                                                
 33                ELAPSEC HEX16.   /                                                                                                
 34                ELAPSEC 17.6     /                                                                                                
 35                ELAPSEC BEST17.6 /                                                                                                
 36                ELAPSEC PD8.6    /                                                                                                
 37                ELAPSEC PK8.6    /                                                                                                
 38                TEST1   $HEX16.  /                                                                                                
 39                TEST2 $HEX16.;                                                                                                    
 40            RUN;                                                                                                                  
                                                                                                                                     
 NOTE: THE FILE SASLIST IS:                                                                                                          
       DSNAME=USER.TS00JY0N.JOB21538.D0000104.?,                                                                                   
       UNIT=SYSOUT,VOLUME,DISP=MOD,BLKSIZE=264,                                                                                      
       LRECL=260,RECFM=VBA,CREATION=2019/11/25                                                                                       
                                                                                                                                     
 NOTE: 8 RECORDS WERE WRITTEN TO THE FILE SASLIST.                                                                                   
       THE MINIMUM RECORD LENGTH WAS 8.                                                                                              
       THE MAXIMUM RECORD LENGTH WAS 17.                                                                                             
 NOTE: THERE WERE 1 OBSERVATIONS READ FROM THE DATA SET WORK.CICS.                                                                   
 NOTE: THE DATA STATEMENT USED THE FOLLOWING RESOURCES:                                                                              
       CPU     TIME -         00:00:00.00                                                                                            
       ELAPSED TIME -         00:00:00.00                                                                                            
       EXCP COUNT   - 16                                                                                                             
       TASK  MEMORY - 5052K (152K DATA, 4900K PROGRAM)                                                                               
       TOTAL MEMORY - 33547K (11040K DATA, 22507K PROGRAM)                                                                           
       TIMESTAMP    - 11/25/2019 8:30:26 AM                                                                                          
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
                                                                                                                                     
 40       !                                                                                                                          
                                                                                                                                     
 NOTE: THE SAS SESSION USED 18.91 CPU SECONDS AND 34699K.                                                                            
                                                                                                                                     
 NOTE: THE ADDRESS SPACE HAS USED A MAXIMUM OF 2532K BELOW THE LINE AND 41548K ABOVE THE LINE.                                       
                                                                                                                                     
 NOTE: SAS INSTITUTE INC., SAS CAMPUS DRIVE, CARY, NC USA 27513-2414                                                                 &lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 25 Nov 2019 13:51:29 GMT</pubDate>
      <guid>https://communities.sas.com/t5/SAS-Programming/Incorrect-packed-decimal-values/m-p/606960#M176345</guid>
      <dc:creator>BrianChapman</dc:creator>
      <dc:date>2019-11-25T13:51:29Z</dc:date>
    </item>
  </channel>
</rss>

