LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous messageNext messagePrevious in topicNext in topicPrevious by same authorNext by same authorPrevious page (August 1996, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 8 Aug 1996 11:12:40 -0400
Reply-To:     MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         "Michael A. Raithel" <MICHAEL.RAITHEL@RAITHM49.CUSTOMS.SPRINT.COM>
Subject:      Re: (MVS) How To Clean Bad Time Stamp Data

George posted:

>In general this is a DATA CLEANING question. > >More specifically, this is a SAS CPE (MXG??) question. > >Every now and then (once in a 1,000,000 records) we get a bad time >value on an SMF generated record (Type72 - variable CPUTCBTM and/or >CPUSRBTM) The value recorded is huge, only ****** are displayed using >a TIME20.4 format in a PROC PRINT. > >I would like to delete any record where CPUTCBTM or CPUSRBTM is not >between 00:00:00.0001 and 24:00:00.0000. I have tried things like: > >if put(CPUTCBTM,HOUR4.) > 24 then delete > >but nothing happened... > >Any thoughts, suggestions, hints... would be appreciated >

George,

You should reexamine your decision to scrub your SMF Type72 data by deleting records with invalid time values! Rather than deleting records with errant CPUSRBTM and/or CPUTCBTM values, you should work with your Systems Programmers to fix the root cause of this problem. By doing so, you will achieve better overall data integrity.

Have the person responsible for installing/running MXG look in the version 13.06 SOURCLIB library in member CHANGES. Have that person look at item #3 under Section "III. MVS Technical Notes after Newsletter TWENTY-EIGHT". Item #3 discusses: "Erratic, very large values in type 72 data may be corrected by APAR OW11733... affecting variables... CPUTCBTM, CPUSRBTM...".

If this APAR applies to your site, then having it applied will bring your Type 72 data back in line; if not, then you should open a dialogue with your systems programmers and IBM personnel. They should document this problem and work towards a fix!

I hope that this suggestion proves helpful now, and in the future!

Of course, all of these opinions and insights are my own, and do not reflect those of my organization or my associates.

++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Michael A. Raithel E-mail: maraithel@mcimail.com Author: Tuning SAS Applications in the MVS Environment ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Well you go your way and I'll go mine; I don't care if we get there on time... ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++


Back to: Top of message | Previous page | Main SAS-L page