WEB-BASED OLTP SYSTEM USING SAS - sasCommunity

WEB-BASED WEB BASED OLTP SYSTEM 

USING SAS 

Haidong Tang (Don) 

Shanghai Baosight Information Technology Co. Ltd. 

May, 2001 

Shanghai Baosight Information Technology Corporation Ltd.

AGENDA 

Introduction to Shanghai Baosight Corp. 

Why Web-based OLTP system 

Web-based OLTP system using SAS 

A Web-based OLTP system using SAS 

Sample SAS program 

Conclusions 


Introduction to 

Shanghai Baosight Corp. 


Shanghai Baosight Information 

Technology Corp. Ltd. 

Established in April 2000 

– Shanghai Baosteel Computer Co. 

– Shanghai Baosteel Software Co. 

– Shanghai Baoni Computer Co. 

Located in Pudong Zhangjiang Hi-Tech 

Park, Shanghai 

800 members (39 PhD ,136 MSc) 



Technology Corp. Ltd. (cont.) 

Close relationship with Shanghai Baosteel 

Group Corporation 



Technology Corp. Ltd. (cont.) 

Partnership with lots of famous companies 



Technology Corp. (cont.) 

Experienced in ERP, Production Control 

System, Network, System integration, ebusiness, 

data analysis, etc. 

Successful cases in the areas of Banking, 

Metallurgy, Communication, Power, 

Trading, Finance, … 

http://www.baosight.com 


Data Strategies Dept. 

Shanghai Baosight Co. 

Majoring in statistical analysis, enterprise 

data warehousing, data mining, quality 

controlling, on-site consulting, system 

integration, and etc. 

More than 5 years on SAS 

Successful cases in Shanghai Baosteel 

Group Corporation, especially in data 

warehousing 


system? 

Why Web-based Web based OLTP system 


What is OLTP 

OLTP is the automation of high-volume, 

repetitive business processes 

Four types operation – query, insertion, 

modification and deletion 

Examples: 

Airline Seat Booking, ATM Withdrawal, 

MIS, etc. 


Characters of traditional OLTP 

Private network 

Centralized hosts, or C/S 

Little downtime 

High security 

Quick response 


Drawbacks of traditional OLTP 

Version control 

System management 

Application extension 

others 


What is Web-based Web based OLTP 

Implementing OLTP functions on Web 

– Query 

– Add 

– Update 

– Delete 

Client/Server Structure 

Taking advantage of Web technologies 


Advantages of Web-based Web based OLTP 

Only Web browser needed on client 

Software distribution 

Version control 

System management 

“block mode with pictures” 

Via private network, or even over Internet 


Essential items for Web-based Web based 

OLTP system developing tools 

Data with integrity definitions 

Multi-user environment 

Methods to author data on Web 

High system performance 

Security control 

Access audit 


Web-based Web based OLTP using SAS 







Access audit 


Integrity constraints 

A set of rules that modifications to data sets 

(or tables) must follow in order to guarantee 

the validity of the data. 

Is essential to OLTP system 

Two types: 

– general constraints (one table) 

– referential constraints (two or more tables) 


How SAS supports integrity 

Since v7 

constraints 

PROC DATASETS 

PROC SQL 

others, as SCL functions … 


Example 

proc sql noprint; 

create table staff 

( id char(5) label='ID number' not null, 

name char(20) label='Name' not null, 

sex char(1) label='Sex' not null check 

( sex in (‘F’ ‘M’)), 

age num label='Age' not null check 

( age between 1 and 100 ), 

salary num label='Salary', 

constraint pk_id primary key (id) 

); 

quit; 


List Constraints 

PROC DATASETS 

PROC SQL 

PROC CONTENTS 

others 


Example 


describe table constraints staff; 

quit; 


Example (continued) 

-----Alphabetic List of Integrity Constraints----- 

Integrity Where 

# Constraint Type Variables Clause 

------------------------------------------------------------------------------------------------- 

1 _CK0001_ Check sex in ('F', 'M') 

2 _CK0002_ Check ((age>=1 and age

RC 

0 

4 

8 

12 

16 

24 

28 

SQL Return Codes 

DESCRIPTIONS 

Completed successfully with no errors. 

The statement executed, but there is a warning. 

Encountered an error. The statement stopped execution. 

Encountered an internal error during compile time. 

Encountered a user error during run time. 

Encountered a system error during run time. 

Encountered an internal error during run time. 


Macro variable 

&SQLRC 

Contains the return code from an SQL 

statement. 

=8, failure execution 

=24, an integrity conflict occurs 







Access audit 


SAS data set (table) 

Fundamentally a file in OS 

Do not provide lock mechanism itself 

Two users can not update the same table at 

the same time (even with different records) 


SAS/Share® 

SAS/Share 

Provides a multi-user environment 

Permits concurrent access 

Is transparency for application developer 

Is easy to administrate the server 







Access audit 


SAS/IntrNet® SAS/IntrNet Components 

Application Dispatcher 

htmSQL 

MDDB report Viewer 

SAS/CONNECT Driver for JAVA 

others 


Application Dispatcher 

One component of SAS/IntrNet 

CGI 

Flexible to program with utilities 

SAS not required on user’s machine 


Web Server 

Br oker 

Diagram of the Process 

Web Browser 

Application 

Ser ver 

SAS 

Pr ogr am 

Shanghai Baosight Information Technology Corporation Ltd. 

Shar e 

Ser ver 

DATA






Access audit 


How to improve system 

performance 

Powerful server 

High bandwidth of network 

etc. 


For application developers 

Deploy a few application servers 

Moderate the amount of data transferring 

over network 

Check data validity at client side 

Predict the frequency of user requests 







Access audit 


Tips on security control 

Authenticate the Broker 

Program with SCL or compiled macro code 

Supply a password to start application server 

Restrict access to program libraries 

Check _RMTUSER and _RMTADDR if 

necessary 

Elaborately test application programs 







Access audit 


Audit trails 

Necessary for mission critical systems 

Usually done in application program with 

extra codes 

Additional application to maintain auditing 

data 


Since v8 

SAS auditing 

Define once, benefit always 

PROC DATASETS ; 

AUDIT SAS-file-name ; 

INITIATE; 

 

 

 


List contents of audit file 

proc contents data=mylib.myfile (type=audit); 

run; 


List data of audit file 

proc print data=mylib.myfile (type=audit) 

run; 


A Web-based Web based OLTP system 

using SAS 


PAC in Baosteel 

PAC - Production Administration Center 

Charges production of the whole company 

Traces the up-to-date production conditions 

Coordinates the different departments 

Holds executives’ routine meeting 


Former MIS system 

Developed by Foxpro 

Long waiting period while authoring 

information 

Difficult to distribute information all over 

the corporation 

Too much paper for report print 


PAC MIS 

A Web-based OLTP system using SAS 

Collects part of data from Baosteel EDW 

Can manually maintain data 

Automatically or manually generate reports 

and graphics for routine meeting and 

management 


Diagram of System Structure 

IBM 9672 

OS/ 390 

DB2 

PAC Net wor k 

Wi n98 

IE5.0 

Intranet 

Backbone 

IBM SP 

AI X 4. 3 

Domino Web Server 

SAS V8 

PAC MIS Application 

Shanghai Baosight Information Technology Corporation Ltd. 

Baost eel 

Ent er pr i s e 

Da t a 

War ehouse 

PAC 

Da t a

A Sample Map from PAC MIS 


Response from users 

Faster then ever to access the report 

Flexible to maintain data 

Easy for authentication 

Can be accessed anywhere on Baosteel 

intranet, or even at home 

Less paper required anymore 


Sample SAS program 


Program structure 

%macro initmap(d,msg,err) 

– initialized the map each time operations finished 

%macro process 

– main process for 4 types of operation 


Use SAS/Share server 

libname gzdata '/home2/dev_sc/gzdata' 

server=bg_sp04.sharesvr; 


%macro process 

%if not %sysfunc(exist(&dsn)) %then 

create table with integrity constraints 

%if &flag ne 1 %then %initmap for the first 

time 


%macro process (cont.) 

%if "&submit"=“QUERY" %then 

proc SQL noprint; 

select * from &dsn where … 

quit; 

decide &sqlrc and process 

%initmap 



%if "&submit"="DELETE" %then 


delete * from &dsn where … 

quit; 


%initmap 



%if "&submit"=“ADD" %then 


insert into &dsn values … 

quit; 


%initmap 



%if "&submit"=“UPDATE" %then 


update &dsn … 

quit; 


%initmap 


Conclusions 


Conclusions 

With SAS/IntrNet®, SAS/Share® and new 

features in Base SAS, SAS can be of an 

ideal tool to develop Web-based OLTP 

system 


The Road Ahead 

Not a “pure” RDBMS 

– System performance 

– Security control 

– Mulit-user environment 

SQL return code should be enhanced 


SAS/IntrNet®, SAS/IntrNet , SAS/Share® 

SAS/Share 

are registered trademarks of 

SAS Institute Inc., Cary, NC. 


Thank you! 


Haidong Tang 

Contact Information 

Data Strategies Dept. 

Shanghai Baosight Information Technology 

Corporation Ltd. 

Email: tanghaidong@baosight.com 

hdtang@263.net 


Questions? 

Questions 


1. Abstract 

WEB-BASED OLTP SYSTEM USING SAS 

Haidong Tang, Data Strategies Dept., 

Shanghai Baosight Information Technology Corp., China 

OLTP (Online Transaction Processing) processing has a long history and has been widely used 

these days. However, as the development of Web technologies, people may tend to migrate these 

traditional OLTP systems to Web. Depending on its Web-enabled technologies, SAS software 

Version 8 has become an ideal tool to develop Web-based OLTP system. 

This paper will introduce the common essential items to realize a Web-based OLTP system and 

the ways SAS software can take to implement such systems. It will discuss in details about the 

technologies employed mainly from the view of an application developer. And it will also give an 

example of an accomplished Web-based OLTP system at Shanghai Baosteel in China. 

2. Introduction 

Why Web-based OLTP 

OLTP is the automation of high-volume, repetitive business processes. These types of transactions 

include short records of a few fields, such as short descriptions, numbers and dates. For end users, 

functions as query, insertion, modification and deletion are an OLTP system may provide to 

manipulate data. Classic examples of OLTP system are Airline Seat Bookings, ATM Withdrawals, 

Production Process Control Systems and Management Information Systems. 

These traditional OLTP systems are based on centralized hosts or C/S platforms with private 

network. This kind of structure may have the some specific advantages as very little downtime and 

high security. However, there are always drawbacks for version control, system management and 

application extension, etc. 

Web-based OLTP system bases on C/S structure, which takes advantage of the Web technologies. 

The Web server is the center of application code and data, and only the Web browsers are required 

on remote workstations. Comparing with the traditional ones, Web-based OLTP systems provide 

end users interfaces of “block mode with pictures”, which is more attractive and easy to handle for 

end users. In Web-based OLTP system, issues of software distribution, version control, and system 

management turn out to be easier. End users can access the server via a private network or over 

the Internet through their ISPs. 

As there are so many advantages to take Web-based OLTP system, SAS developers are likely to 

adopt SAS software as a tool for developing Web-based OLTP systems. 

Essential items for OLTP systems 

Today, there are various Web-based OLTP systems developed using various developing tools. 

Examples of Web-based OLTP systems can be Travel Reservations, Online Stock Trading, Home 

Banking and MIS. But what are the common essential items of these systems? 

From the view of an application developer, following aspects should be taken into considerations 

while designing Web-based OLTP system. 

a. Data with integrity definitions, which reflect the real world situations;

. A multi-user environment for users query and update data simultaneously; 

c. Methods for authoring data on Web; 

d. High system performance, which means high-volume data with quick response time; 

e. Security control; 

f. Access audit. 

To develop a Web-based system using SAS software, SAS should have some corresponding 

methods to implement all these items. Actually ever since Version 8, SAS software has become an 

ideal tool for developing Web-based OLTP systems. Well, let’s take a close look at all these items 

and the way we can go. 

3. WEB-BASED OLTP USING SAS 

Define data with integrity constraints 

Integrity constraints, which are essential for OLTP, are a set of rules that modifications to data sets 

(or tables) must follow in order to guarantee the validity of the data. Though not a “pure” 

relational database system, SAS now supports integrity constraints quite well. There are several 

flexible ways to create and delete integrity constraints, such as the DATASETS procedure, the 

SQL procedure, and SCL functions. Among all these ways we prefer the SQL procedure, for SQL 

is a standard way to access data and may easy for migration between different systems. For detail 

descriptions of constraints definitions, please refer “SAS Online Document V8”. 

Here is an example of creating a table of STAFF with integrity constraints: 


create table staff 

( id char(5) label='ID number' not null, 

name char(20) label='Name' not null, 

sex char(1) label='Sex' not null check ( sex in (‘F’ ‘M’)), 

age num label='Age' not null check ( age between 1 and 100 ), 

salary num label='Salary', 

constraint pk_id primary key (id) 

); 

quit; 

The constraints as “primary key”, “not null” and “check” guarantee the consistency of the table 

STAFF. For example, the constraint PK_ID guarantees there will always be a unique ID number. 

It is obvious that these kinds of constraint are essential to an OLTP system, as they make data 

comply with the rules in real world situations. By capturing the SQL return codes, we can do 

further jobs on data processing. In SAS, the macro variable &SQLRC contains the status values 

after the SQL procedure statement has been executed. 

Though not detailed classified as in other database products, the available SQL return codes are as 

followed. 

0 Completed successfully with no errors. 

4 The statement executed, but there is a warning. 

8 Encountered an error. The statement stopped execution. 

12 Encountered an internal error during compile time. 

16 Encountered a user error during run time. 

24 Encountered a system error during run time. 

28 Encountered an internal error during run time. 

Generally, a return code greater than or equal to 8 can be considered as a failure execution of the 

statement. And once there is an integrity conflict, system returns 24. 

So when the same ID inserts to table STAFF, or there are some other integrity conflict happens,

the execution will abort with a return code &SQLRC=24. Therefore, the application can prompt a 

proper message for end users to take further actions on their data. 

To list all the constraints in a data set, use PROC CONTENTS or PROC SQL. For example, 


describe table constraints staff; 

quit; 

The constraints of table STAFF is as followed: 

-----Alphabetic List of Integrity Constraints----- 

Integrity Where 

# Constraint Type Variables Clause ---------------------------------------------------- 

---------------------------------------------------------------------------------- 

1 _CK0001_ Check sex in ('F', 'M') 

2 _CK0002_ Check ((age>=1 and age

Web 

Browser 

Web 

Server 

Broker 

CGI 

User of Web-based OLTP system sends a request for application program to Web Server; 

Broker CGI of the SAS/IntrNet® then dispatches the request to the SAS Application Server; 

The Application Server invokes the Application Program and passes parameters to it; 

The Application Program then adds, updates, deletes or queries data through a share server; 

The Application Program returns an HTML page with operation status to Web Server; 

Web Server returns the final page to user. 

For more information on Application Dispatcher, please consult “SAS Online Document V8”. 


Application 

Server(s) 

Application 

Program 

Share 

Server 

System performance, especially response time, is very sensitive to end users. Web-based OLTP 

system does have some weaknesses concerning this issue, as transaction predictability is far from 

a reality. It is certain that relying on powerful Web servers for high-volume processing and high 

bandwidth of network for heavy traffic, the painful problem could be eased. However, from the 

application developer side, some measures still can be taken under a certain decided system 

environment. 

a. Deploy a few Application Servers 

SAS application server provides three types of service: socket, pool and launch. To improve the 

response time, it is suggested that socket service with more application servers should be 

deployed. As the servers are running by the time client requests appears, clients do not have to 

wait for a server to start. It is quite effective in a multi-user environment. 

b. Moderate the amount of data transferring over network 

How much data can be placed on one application map? As much as one wants once he uses POST 

method instead of GET. How much would be appropriate? No exact answers. But the fact is, the 

more data the user operates at a time, the slower response time it will be. So it is important to 

moderate the amount of data transferring over network according to the real situation. 

Instead of placing a large amount of data on one map, it can be shared in several consecutive maps 

with separated transactions to operate. Therefore there are normally two ways to fulfill the task, 

Saving information in a temporarily SAS data set on server; 

Using SESSION in Version 8.0. 

c. Check data validity at client side 

It is suggested that all data transferred to server should be correct in format and in content if it is 

possible. JavaScript or VBScript therefore can be assisted in checking the data validity before a 

Web form is submitted. 

d. Predict the frequency of user requests 

Users may use the application in a varied period of time. It is necessary to predict the frequency of 

user requests at different time period, so that some effective measures can be taken to avoid traffic 

jam. 

Data


Security is always a very thorny issue for Web applications. It is a complex issue that may concern 

user authentication, authorization, communications security and writing secure applications. 

Mentioned here are a few, 

a. Authenticating the Broker in a Web server, so that only authenticated users can invoke Broker 

to use the applications; 

b. Using SCL or compiled macro code to prevent user from reading the source program under 

with _DEBUG=131; 

c. Supplying a password when starting the application server; 

d. Restricting access to program libraries; 

e. Checking _RMTUSER and _RMTADDR to establish a user defined access control if it is 

necessary; 

f. Test the applications carefully before being put into production, so as to prevent any “back 

doors” in application programs. 

Audit trial 

For mission critical OLTP system, audit trial is a necessity. In traditional OLTP system, this is 

done with additional code in application programs. For example, after a successful deletion 

(decided by SQL return code), we may insert the record, with additional information as operator 

id, time of operation, to an audit table. Having been enhanced, SAS V8 itself enables to log 

updates to a SAS data file in a separate audit file each time an observation is added, deleted, or 

updated. This means information will be automatically added to the audit file about who made the 

modification, what was modified, and when. 

The audit trail is initiated with the AUDIT statement in PROC DATASETS. 

PROC DATASETS ; 

AUDIT SAS-file-name ; 

INITIATE; 

 

 

 

The following example code shows the way to create the audit file MYLIB.MYFILE.AUDIT to 

log updates to the data file MYLIB.MYFILE.DATA, storing all available record images. 

proc datasets library=MyLib; 

audit MyFile alter=MyPassword; 

initiate; 

run; 

PROC CONTENTS can be used to review the contents: 

proc contents data=Mylib.Myfile (type=audit); 

run; 

To check the audit file, use PROC PRINT: 

proc print data=Mylib.Myfile (type=audit) 

run; 

4. A WEB-BASED OLTP SYSTEM USING SAS

Situation 

Shanghai Baosteel is the largest and the most advanced iron and steel making corporation in 

China. Production Administration Center (PAC) at Baosteel is the department that charges 

everyday production of the whole corporation. It keeps on tracing the up-to-date production 

conditions and coordinates the different departments upon the information that they get. 

Meanwhile, there is a routine meeting for executives to make decisions upon information gathered 

by PAC. 

PAC used to depend on a system of Foxpro to fulfill its duty. The users complained that, 

a. Long waiting period while authoring information at the executives routine meetings; 

b. Difficult to distribute information all over the corporation; 

c. Too much paper for report printing. 

System introduction 

The Web-based Management Information System for Production Administration Center (PAC 

MIS) is a system developed using SAS software. PAC MIS automatically grabs the required data 

from data warehouse by a batch job in midnight, and later users at PAC still can manually 

maintain the data on Web. Almost reports and analytic graphics for executives’ meeting and daily 

management can be generated manually or automatically in HTML files, which are directly 

authored from Web server. 

The whole system has been deployed on IBM SP, an admitted mission critical machine for highvolume 

processing. The IBM SP has been linked to Baosteel ATM backbone, while IBM Domino 

Web server, SAS V8 for AIX and related software have been installed on it. As the enterprise data 

warehouse has been built on the same machine using SAS software, it provides an ideal data 

source environment for PAC MIS. 

The following diagram illustrates the system configuration. 

Data warehouse 

Baosteel Intranet 

100M ATM Backbone Batch job 

IBM 

SP 

SAS V8 

Domino Web server 

PAC MIS applications 

OLTP data 

PAC 

Users MS IE5.0 / Windows 98 

PAC MIS consists of four subsystems, which are the information authoring, the authentication 

management, the online data management and the batch job. The online data management 

subsystem is designed and established on Web-based OLTP concept, and is the core of the whole 

system. 

One map in the online data maintenance subsystem has been showed below. Authenticated users 

can easily query, add, update and delete the daily raw material data on their browsers.

Response from user 

After PAC MIS has been finished and put into production, it receives high reputation from users. 

Comparing with the old system, PAC MIS has the following advantages. 

a. Faster to access the report, as most of them have already been generated in HTML files; 

b. Flexible to maintain data; 

c. Easy for authentication; 

d. Can be accessed anywhere on Baosteel intranet, or even at home through a telephone line; 

e. Less paper required anymore. 

5. CONCLUSIONS 

With SAS/IntrNet®, SAS/Share®, SAS can be of great tool to develop Web-based OLTP system. 

However, it is still a long way to go for establishing mission critical OLTP systems. For SAS, not 

a “pure” RDBMS, may appear to be less effective in handling large amount of data and be a little 

bit awkward for users accessing through SAS/Share®. SAS has its flexible enhanced SQL, but the 

return code has been superficially classified, which can lead to some ambiguities. 

SAS has now announced its SAS/SPDS® for higher performance, better access control. 

Depending on high performance machine, it can be convincing that applying SAS/SPDS® into 

Web-based OLTP system will be of great help to ease some of the issues. 

6. CONTACT INFORMATION 

The author can be contacted at: 

Haidong Tang 

Baosight Corporation

No. 688 Fujin Road, Baoshan District 

201900 Shanghai 

P.R.China 

Email: tanghaidong@baosight.com 

7. REFERENCES 

SAS Online Document, V8 SAS Institute Inc., Cary, NC. 

Application Dispatcher, Version 8.0 http://www.sas.com/rnd/web/intrnet/dispatch/index.html 

SAS/IntrNet®, SAS/Share®, SAS/SPDS® are registered trademarks of SAS Institute Inc., Cary, 

NC. 

8. APPENDIX – A SAMPLE SAS PROGRAM 

Following is the program showing query, addition, update, and deletion in a Web-based OLTP 

system. It is a SAS program, but it is recommended to apply SCL program for a production 

system. To be clarity in structure, it also has been tailored from the original code. 

%macro initmap(d,msg,err); 

data _null_; 

file _webout; 

format dt datetime.; 

length s $ 200; 

msg=symget('msg'); 

yyyymmdd=symget('yyyymmdd'); 

dt=symget('dt'); 

dd=symget('dd'); 

tt=symget('tt'); 

put 'Content-type: text/html'; 

put; 

put ''; 

put ''; 

put 'PAC – RAW MATERIAL DATA'; 

put ''; 

put ''; 

put ''; 

put ''; 

put 'PAC MIS (MAP 1)'; 

put 'RAW MATERIAL MANAGEMENT'; 

put '' dd tt ''; 

/* change GET into POST when put into production */ 

put ''; 

put ''; 

put '

* application server service name */ 

put ''; 

/* program name */ 

put ''; 

/* debug status */ 

put ''; 

put ''; 

put ''; 

s='DATE: '; 

put s; 

put 'UNIT: TONS'; 

put ''; 

put ''; 

put ' '; 

put 'TODAY'; 

put 'ACCUMULATED'; 

put 'STORAGE'; 

put ''; 

put ''; 

put 'IRON ORE'; 

s=''; 

put s; 

s=''; 

put s; 

s=''; 

put s; 

put ''; 

put ''; 

put ''; 

put ""; 

put ""; 

put ""; 

put ""; 

run; 

%mend initmap; 

%macro process; 

/* Create a table with integrity constraints */ 

%if not %sysfunc(exist(&dsn)) %then 

%do; 


create table &dsn 

(date_prc char(8) format=$8. label='processing date' primary key, 

QUANT_Iron_day num format=11. label='day iron ore' check (quant_iron_day between 1 and 1000 ), 

QUANT_Iron_acc num format=11. label='acc iron ore' check (quant_iron_acc between 1 and 10000 ), 

QUANT_Iron_store num format=11. label='str iron ore' check (quant_iron_store between 1 and 10000 

),

last_upd num format=datetime22. label='date last update' not null, 

_rmtuser char(36) format=$36. label='user operated' not null, 

_rmtaddr char(15) format=$15. label='IP address' not null); 

quit; 

%end; 

/* first time the program be called */ 

%if &flag ne 1 %then 

%do; 

%initmap(0,Welcome to PAC MIS!); 

%goto endproc; 

%end; 

/* user pressed QUERY button on the map */ 

%if "&submit"="QUERY" %then 

%do; 

%initmap(&date_prc,QUERY FINISHED!); 


%end; 

/* user pressed DELETE button on the map */ 

%if "&submit"="DELETE" %then 

%do; 


delete * from &dsn where date_prc="&date_prc"; 

quit; 

%if &sqlrc ge 8 %then %do; %initmap(0,ERROR WHILE DELETE! SQLRC=&sqlrc,1); %end; 


%end; 

/* user pressed ADD button on the map */ 

%if "&submit"="ADD" %then 

%do; 


insert into &dsn values 

(date_prc=“&date_prc”, 

quant_iron_day=&QUANT_Iron_day, 

QUANT_Iron_acc=&QUANT_Iron_acc, 

QUANT_Iron_store=&QUANT_Iron_store, 

last_upd=“&last_upd”, 

_rmtuser=“&_rmtuser”, 

_rmtaddr=“&_rmtaddr” 

); 

quit; 

%if &sqlrc=24 %then 

%do; %initmap(&date_prc,&date_prc%str(DATA ALREADY EXIST!),1); %goto endproc; %end; 

%if &sqlrc ge 8 %then 

%do; %initmap(&date_prc,ERROR WHILE ADDING! (SQLRC=&sqlrc),1); %goto endproc; 

%end; 

%initmap(&date_prc,ADD FINISHED!); 


%end; 

/* user pressed UPDATE button on the map */ 

%if "&submit"="UPDATE" %then

%do; 


update &dsn 

set 

(date_prc=“&date_prc”, 

quant_iron_day=&QUANT_Iron_day, 

QUANT_Iron_acc=&QUANT_Iron_acc, 

QUANT_Iron_store=&QUANT_Iron_store, 

last_upd=“&last_upd”, 

_rmtuser=“&_rmtuser”, 

_rmtaddr=“&_rmtaddr” 

) 

where date_prc="&date_prc"; 

quit; 

%if &sqlrc ge 8 

%then %do; %initmap(&date_prc,ERROR WHILE UPDATE! (SQLRC=&sqlrc),1); %goto 

endproc; %end; 

%initmap(&date_prc,UPDATE FINISHED!); 

%end; 

%endproc: 

%mend process; 

/*--------------------------------------------*/ 

/* The program runs from here! */ 

/*--------------------------------------------*/ 

%global flag yyyymmdd dt last_upd dd tt; 

/* access data through a share server */ 

libname gzdata '/home2/dev_sc/gzdata' server=sharesvr; 

%let dsn=gzdata.gz0001; 

/* check if the user has the access right, decided by _RMTUSER */ 

%checkuser(PACUSER); 

data _null_; 

yyyymmdd=compress(put(date(),yymmdd10.),'-'); 

dd=put(date(),yymmdd10.); 

tt=put(time(),time8.); 

dt=datetime(); 

last_upd=datetime(); 

call symput('yyyymmdd',yyyymmdd); 

call symput('dt',dt); 

call symput('dd',dd); 

call symput('tt',tt); 

call symput('last_upd',last_upd); 

run; 

%process;

WEB-BASED OLTP SYSTEM USING SAS - sasCommunity

Create successful ePaper yourself

Delete template?

Save as template?