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 (February 1996, week 2)Back to main SAS-L pageJoin or leave SAS-L (or change settings)ReplyPost a new messageSearchProportional fontNon-proportional font
Date:   Mon, 12 Feb 1996 21:15:18 1000
Reply-To:   "Alex M. Wolf" <wolfam@WERPLE.NET.AU>
Sender:   "SAS(r) Discussion" <SAS-L@UGA.CC.UGA.EDU>
From:   "Alex M. Wolf" <wolfam@WERPLE.NET.AU>
Subject:   Re: AF/FRAME 6.11 on Win 3.11 Problems.
Comments:   To: 0006974523@mcimail.com

Jules and SAS-L members,

Thanks for the suggestions to my problem.

I have solved the problem in a way that was unexpected by myself:

One of Windows 3.11's main claim to fame was it's 32 bit File Access facility, unfortunately slightly flaky in some circumstances. With it enabled, the bizarre DSID resolution occurred, with it switched off, no problems at all !

It appears that SAS 6.11 does strange things for win 3.11 and probably was never tested on this version of windows.

Thanks again all

Alex Wolf

---------- From: Jules Bosch[SMTP:0006974523@mcimail.com] Sent: Monday, 12 February 1996 2:19 To: Alex M. Wolf Subject: Re: AF/FRAME 6.11 on Win 3.11 Problems.

Alex,

Please excuse any response I provide if it seems trite. If you are running TESTAF, are there any SUBMIT blocks in the SCL behind the frame? If so, the code within the SUBMIT block will not execute. Therefore, run the frame entry from the DM Program Editor via the command af c=libanme.catalog.framename.frame. Also, is the data set already opened with a mode other than 'I' (read only) which might have it locked up?

Let me know what happens.

Jules Bosch

jules_bosch@mcimail.com


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