LISTSERV at the University of Georgia
Menubar Imagemap
Home Browse Manage Request Manuals Register
Previous (more recent) messageNext (less recent) messagePrevious (more recent) in topicNext (less recent) in topicPrevious (more recent) by same authorNext (less recent) by same authorPrevious page (May 1996, week 3)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:         Thu, 16 May 1996 14:56:47 -0700
Reply-To:     Chris Hulley <CHulley@NITGRMC8.TELECOM.COM.AU>
Sender:       "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:         Chris Hulley <CHulley@NITGRMC8.TELECOM.COM.AU>
Organization: Telstra
Subject:      Re: stats after copy on mvs/esa
Comments: To: IBM-MAIN@UA1VM.UA.EDU

Kenneth Hobson wrote: > > In a clist I copy a sequential file to a pds.< The member does not have statistics. How can I get them please? > > e.g. copy 'neutral.umtr121.choices.log' 'design.choices.log(umtr121)' nonum< > I can only get stats after I edit and save them member umtr121.< > More info:< I run the clist to alloc the neutral file and SAS v6.08 has the filestat > option turned on. After I call sas and exit sas the clist copies the file as< above. > < Idea: > Maybe use the pds somehow?< I want this to happen so that it is not visible to the executor of the clist. > e.g. in the clist< after the copy, > pds 'design.choices.clist(umtr121' e< stats on > save< end > > If pds could have the stats on, save, and end immediately. I don't see how< though. > < Any ideas? TIA > < email umtr121@dsibm.okladot.state.ok.us > The statistics are an ISPF feature; the best way to keep them is by using the ISPF Library Management copy feature, LMCOPY, e.g.

/* REXX */ "ISPEXEC LMINIT DATAID(D01) DATASET('SYS3.TEMP.COPY1') ENQ(SHR)" "ISPEXEC LMINIT DATAID(D02) DATASET('SYS3.TEMP.COPY2') ENQ(SHR)" "ISPEXEC LMCOPY FROMID("D01") FROMMEM(TRY) TODATAID("D02") REPLACE" "ISPEXEC LMFREE DATAID("D01")" "ISPEXEC LMFREE DATAID("D02")"

Hope this helps, -- Regards, Chris Hulley ADC Consultants Sydney -------------- "Isn't it great how in MVS, we don't get messages like 'DB2 caused a general protection fault in module MVS at offset 00000:62347, your application will be terminated' every half hour ?"


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