BookmarkSubscribeRSS Feed
ArtC
Rhodochrosite | Level 12
Can anyone tell me why sashelp.vgopt and PROC GOPTIONS do not necessarily yield the same result? (SAS9.2 under Windows)

[pre]goptions reset=all dev=win;
proc goptions option=hpos;
run;
proc print data=sashelp.vgopt(where=(optname='HPOS'));
var optname setting;
run;
[/pre]
This is just one option that is different. There are others. The SASHELP.VGOPT view seems to have the correct values.
3 REPLIES 3
Ksharp
Super User
Hi.Art Carpenter.
Perhaps you need to talk to Technical Group.
I also think these both are identical.

Regards.

Ksharp
data_null__
Jade | Level 19
Not WHY but it appears the dictionary or view is looking at the driver info LROWS and LCOLS.

[pre]
GDEVICE procedure
Listing from SASHELP.DEVICES - Entry WIN

Orig Driver: WIN Module: SASGDDMX Model: 26001
Description: Microsoft Windows Display Type: CRT
*** Institute-supplied ***
Lrows: 10 Xmax: 15.000 IN Hsize: 0.000 IN Xpixels: 1280
Lcols: 35 Ymax: 12.000 IN Vsize: 0.000 IN Ypixels: 1024
Prows: 0 Horigin: 0.000 IN
Pcols: 0 Vorigin: 0.000 IN

[/pre]
Andre
Obsidian | Level 7
Art

With the old manner
[pre]
proc gdevice catalog=sashelp.devices browse nofs;
list win ;
quit;
[/pre]

or with this
[pre]
proc goptions short;run;
[/pre]



you have it , but not alone !

Andre 😉

SAS Innovate 2025: Register Now

Registration is now open for SAS Innovate 2025 , our biggest and most exciting global event of the year! Join us in Orlando, FL, May 6-9.
Sign up by Dec. 31 to get the 2024 rate of just $495.
Register now!

How to Concatenate Values

Learn how use the CAT functions in SAS to join values from multiple variables into a single value.

Find more tutorials on the SAS Users YouTube channel.

SAS Training: Just a Click Away

 Ready to level-up your skills? Choose your own adventure.

Browse our catalog!

Discussion stats
  • 3 replies
  • 1185 views
  • 0 likes
  • 4 in conversation