The top four user requested grid features delivered with sas grid manager 9 4
This presentation is the property of its rightful owner.
Sponsored Links
1 / 31

The Top Four User Requested Grid Features Delivered With SAS Grid Manager 9.4 PowerPoint PPT Presentation


  • 134 Views
  • Uploaded on
  • Presentation posted in: General

The Top Four User Requested Grid Features Delivered With SAS Grid Manager 9.4. Doug Haigh SAS Institute. Summary of New Features. Option Sets Workspace Servers launched using the grid Logging SASGSUB enhanced wait. Grid Options Sets. Managing users and grid applications in 9.3.

Download Presentation

The Top Four User Requested Grid Features Delivered With SAS Grid Manager 9.4

An Image/Link below is provided (as is) to download presentation

Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -

Presentation Transcript


The top four user requested grid features delivered with sas grid manager 9 4

The Top Four User Requested Grid Features Delivered With SAS Grid Manager 9.4

Doug Haigh

SAS Institute


Summary of new features

Summary of New Features

  • Option Sets

  • Workspace Servers launched using the grid

  • Logging

  • SASGSUB enhanced wait


Grid options sets

Grid Options Sets


Managing users and grid applications in 9 3

Managing users and grid applications in 9.3

Specific users

using specific applications

needing specific grid options

+

One set of grid options per SAS application server context

=

Multiple SAS application server contexts


An example

An example…


What is needed

What is needed

DIS Grid Options

SAS Options:-memsize 256

Resources:<none>

Grid Options:queue=normal

Risk

DIS

SASGSUB

DIS

SASGSUB

SASGSUB OPTIONS

SAS Options:-memsize 0

Resources:GSUB

Grid Options:queue=night

Finance


Same deployment in 9 4

Same deployment in 9.4

Using Grid

Options Sets


Grid options sets1

Grid Options Sets

  • Grouping of options commonly used by grid

  • Mapped in a grid server to a grid application for a user

  • Can be mapped multiple times

  • Override default options


Logical grid server metadata

Logical Grid Server Metadata

Default options


Grid options set mapping wizard

Grid Options Set Mapping Wizard

Where grid options sets are managed


Grid options set editor

Grid Options Set Editor


How it is used

How it is used

  • New gridoptset option on grdsvc_enable

    grdsvc_enable(_All_,

    "server=SASApp;

    gridoptset='MyAppGridOpts'")

  • Client applications that generate grid code

  • Client applications that submit to grid

  • Object Spawner


Grid launched workspace servers

Grid-launched Workspace Servers


In 9 3 using the grid in eg

In 9.3, using the grid in EG

Workspace

Server

EG

EG/AMO Grid macros

Grid

Server

GRID


Now in 9 4

Now in 9.4…

Workspace

Server

GRID

EG


New workspace server load balancing option

New workspace server load balancing option

1

2


Logging enhancements

Logging Enhancements


In 9 3 debugging involved

In 9.3, debugging involved…

  • Different debug options

    • TCPDEBUG

    • CNTDEBUG

    • SAS_GRID_DEBUG

    • STDOUTPUT

    • VERBOSE

    • SAS Logging Facility

  • Different debug output

    • TCPDFILE

    • CNTDFILE

    • SAS LOG

    • SPAWNER.DAT

    • SASGRID.STDOUT

    • SASGRID.STDERR

    • SAS Logging Facility


Now in 9 4 debugging is standardized

Now in 9.4, debugging is standardized

  • SAS Logging Facility

  • SASGRID script log file


Sasgsub wait enhancements

SASGSUB Wait Enhancements


In 9 3 waiting for grid job using sasgsub

In 9.3, waiting for grid job using SASGSUB

sasgsub –gridsubmitpgmMyProgram.sas

–gridwait

<parse output to get job-id & job-dir>

sasgsub–gridgetresults <job-id>

<copy log & output from job-dir>

<parse job.info file for job rc>

<return job rc as script rc>


Now in 9 4 the script is

Now in 9.4, the script is…

sasgsub –gridsubmitpgmMyProgram.sas

–gridwaitresults

–gridwaittimeout 3600

rc=$?

(or rc=%ERRORLEVEL% for Windows)


Summary of new features1

Summary of New Features

  • Option Sets

  • Workspace Servers launched using the grid

  • Logging

  • SASGSUB enhanced wait


How does it work

How does it work?

Default Values

SAS Options -memsize 256M -DBCS

Required Resources SASApp

Grid Options queue=normal

Options Set Values

SAS Options -memsize 0

Required Resources Teradata

Grid Options queue=priority

Merged Option Values

SAS Options -memsize 256M –DBCS –memsize 0

Required Resources SASAppTeradata

Grid Options queue=normalqueue=priority

Resulting Option Values

SAS Options-DBCS -memsize 0

Required ResourcesSASApp Teradata

Grid Optionsqueue=priority


Where options sets live

Where Options Sets live


Application names in mapping wizard

Application Names in Mapping Wizard

  • Name of folder in /System/Applications

  • Configuration set property indicating application was grid capable


Grid workspace servers options sets

Grid Workspace Servers & Options Sets

  • For Object Spawner to get Options Set, it needs client application name

    New client connection (6) accepted from server port 8594 for user

    ...

    for APPNAME=SAS Data Integration Studio.

  • Application name must match folder name


What about old applications

What about Old Applications?

  • Create a folder under /System/Applications

  • Set isGridCapable keyword

  • If name is different, set name on isGridCapable keyword

    • isGridCapable:SAS Enterprise Miner Mid-Tier

    • isGridCapable:*SAS Enterprise Miner

    • isGridCapable:SAS Enterprise Miner*

    • isGridCapable:*SAS Enterprise Miner*


Keywords

Keywords


Helping the match making process

Helping the match-making process

  • Make sure application sends APPNAME to spawner

  • Make sure APPNAME matches

    • Folder name

    • isGridCapable pattern

  • Make sure a mapping exists for app server and user


  • Login