Hi Jit,

why not using the SAS macros %SYSRPUT and %SYSLPUT , you can download them for free from www.sas.com

Ciao. Mauro.

MATRIX Castelfranco Veneto - ITALY

<charles_s_patridge@my-deja.com> wrote in message 8kcpa7$odm$1@nnrp1.deja.com... > Dear Jit, > > Check my web site (www.sasconsig.com) and look under tips and > techniques (Table of Contents - left frame). > > There are a couple of possible tips that may help you. > > HTH, > Charles Patridge > Email: Charles_S_Patridge@prodigy.net > > > In article <85256918.004DF8DF.00@paerscngw01.metro.prudential.com>, > Jit Bhattacharya <jit.bhattacharya@PRUDENTIAL.COM> wrote: > > Hello, > > > > I need some help with porting macro variables created by an SCL code > on the PC > > to a mainframe host(MVS). > > > > The portion of SCL code that creates the macro vars is - > > > > length string $ 50 > > m_var $ 8 > > ; > > array scl_var{*} $ userid stcode comp ; > > string = 'userid stcode comp' ; > > > > do i=1 to dim(scl_var) ; > > m_var= scan( string,i ) ; > > call symput( m_var,scl_var{i} ) ; > > end ; > > > > The macro vars USERID, STCODE, and COMP are created in the PC > environment. > > However, I need these to be created on the mainframe side. > > At the time the SCL executes, I have a MVS/TSO session open with > SAS/CONNECT. > > Further into the SCL code, I copy source code into the preview buffer > that is > > executed on the mainframe. Since this procedure does not resolve SCL > variables > > as from within a SUBMIT block, I need to convert SCL variables to > macros on MVS. > > > > Any help would be much appreciated. > > > > Jit > > > > -- > Charles Patridge - PDPC, Ltd. > 172 Monce Road - Burlington, CT 06013 USA > Phone: 860-673-9278 or 860-675-9026 > Email: Charles_S_Patridge@prodigy.net - Web: www.sasconsig.com > > > Sent via Deja.com http://www.deja.com/ > Before you buy.