Tuesday, September 3, 2013

Photo Re-size

Crop your Photos online

Sunday, February 24, 2013

Android Fast Application building tools

There are some tools available free to build Android application easily.

http://beta.appinventor.mit.edu - This is very interesting site developed my MIT. You can learn new way of programming.

http://www.appsgeyser.com  - Tool to build apps easily

Thursday, September 6, 2012

Subsystem Details:


Creating a Subsystem Description
You can create a subsystem description in two ways. You can copy an existing
subsystem description and change it, or you can create an entirely new description.
The following are two approaches you can use:
v Copying an existing subsystem description
1. Create a duplicate object, CRTDUPOBJ, of an existing subsystem
description. (You can also use the WRKOBJ or WRKOBJPDM commands.)
2. Change the copy of the subsystem description.
See Appendix C. IBM-Supplied Object Contents, for examples.
v Creating an entirely new subsystem description
1. Create a subsystem description (CRTSBSD).
2. Create a job description (CRTJOBD).
3. Add work entries to the subsystem description.
a. ADDWSE (Add workstation entry)
b. ADDJOBQE (Add job queue entry)
c. ADDCMNE (Add communications entry)
d. ADDAJE (Add autostart job entry)
e. ADDPJE (Add prestart job entry)
4. Create a class (CRTCLS).
5. Add routing entries to the subsystem description (ADDRTGE).
Starting a Subsystem
To start a subsystem, use the Start Subsystem (STRSBS) command or the Work
with Subsystem Description (WRKSBSD) command. To use the STRSBS
command, specify the following:
STRSBS SBSD (SBSD=library/subsystem
description name)
For example
STRSBS MYLIB/MYSTORE
How a Subsystem Starts
When a subsystem starts, the system allocates several items and starts autostart
and prestart jobs before it is ready for work.
1. After the Start Subsystem (STRSBS) command is issued, the system allocates
the following items, finding the information in the subsystem description:
v Pools of main storage
v Display stations
v Communications devices
v Job queues
2. Next, the autostart jobs and prestart jobs are started and the subsystem is
ready for work. Figure 3 shows what occurs when a subsystem starts.
Chapter 4. Subsystems 83
Subsystem Monitor Job
The subsystem monitor job provides control over an active subsystem. It provides
functions such as initiating, controlling, and ending jobs. Several subsystem monitor
jobs may run on a system at any given time.
Subsystem monitor jobs are identified by type SBS on the Work with Active Jobs
display. You can see this by using the Work with Active Jobs (WRKACTJOB)
command.
Note: IBM supplies two complete controlling subsystem configurations: QBASE
(the default controlling subsystem), and QCTL. Only one controlling
subsystem can be active on the system at one time. The Controlling
Subsystem Description (QCTLSBSD) system value determines

Saturday, July 21, 2012

Wednesday, November 9, 2011

Android Fundamentals

Before directly going to the application development, I thought its better to read something on the Android OS. It was quite interesting to me when I understand that each applications in this OS is treated as different user with different permissions to the assoicated files.More over this OS runs with Linux Kernal as a multi-user Linux system in which each application is a different user.

•By default, the system assigns each application a unique Linux user ID (the ID is used only by the system and is unknown to the application). The system sets permissions for all the files in an application so that only the user ID assigned to that application can access them.

•Each process has its own virtual machine (VM), so an application's code runs in isolation from other applications.

•By default, every application runs in its own Linux process. Android starts the process when any of the application's components need to be executed, then shuts down the process when it's no longer needed or when the system must recover memory for other applications

•It's possible to arrange for two applications to share the same Linux user ID, in which case they are able to access each other's files. To conserve system resources, applications with the same user ID can also arrange to run in the same Linux process and share the same VM (the applications must also be signed with the same certificate).

•An application can request permission to access device data such as the user's contacts, SMS messages, the mountable storage (SD card), camera, Bluetooth, and more. All application permissions must be granted by the user at install time.

Refer Application Fundamentals

Saturday, November 5, 2011

Android Applications Development


Next years smart phones will be driven be Android OS.Android is a software stack for mobile devices that includes an operating system, middleware, and key applications. The Android SDK provides the tools and libraries necessary to begin developing applications that run on Android-powered devices.

I started with the Android application development.For the the initial set up ,going through the Youtube Tutorials. The Android application development tools are Eclipse and Android sdk. Some of the links recently I tried to follow.

http://code.google.com/android/

You can download the Android sdk from the following link http://developer.android.com/sdk/index.html
http://developer.android.com/index.html

and also the youtube videos from http://www.thenewboston.com/







Saturday, August 13, 2011

AS400 SQL STORED PROCEDURES AND EXTERNAL STORED PROCEDURES EXAMPLES

A stored procedure is a subroutine available to applications accessing a relational database system. Stored procedures are actually stored in the database data dictionary. In AS400 it is stored in SYSROUTINES and SYSPARMS tables.

AS400 the stored procedures cane called from SQLRPGLE program or from STRSQL utility screen. Stored procedures may return result sets i.e. the results of a SELECT statement,or it can retun the paramters declared as OUT. Result sets can be processed using cursors, by other stored procedures, by associating a result set locator, or by applications. Stored procedures may also contain declared variables for processing data and cursors that allow it to loop through multiple rows in a table. Stored procedure languages typically include IF, WHILE, LOOP, REPEAT, and CASE statements, and more. Stored procedures can receive variables, return results or modify variables and return them, depending on how and where the variable is declared

There are two type of stored procedures in AS400 - External stored procedures and SQL stored procedures. While creating the external Procedures an external program( CL,RPGLE,COBOL,C etc) will linked to procedure. But in SQL stored procedures all the statements will be SQL statements. The AS400 stored procedures can also be called from .NET,JAVA,VB etc other front end applications.

External Stored Procedure


In the below example an external procedure is created with CREATE PROCEDURE statement in the STRSQL utility. The program CHECKCUST( RPGLE - for checking the customer is present or not ) is linked to the procedure so that when a call comes to the procedure, indirectly procedure invokes the program with passed parameters. Below program (CHECKCUST) returns a flag(RECFND) which procedure passes to the calling program PROTESTPGM (SQLRPGLE).

SOURCE : Procedure calling program (PROTESTPGM)
-----------------------------------------------

The real cases the procedures are called from the front-end applications. But we can also call the procedures from SQLRPGLE in AS400 itself.


SOURCE: CHECKCUST ( RPGLE Program attached to Procedure)
-------------------------------------------------------



CREATE PROCEDURE :


The below SQL statment includes the language of the external program,External program Name/Library. For more Stored Procedures

CREATE PROCEDURE DAVNAV1/PROCCHECKCUST(IN CUSTNUM DECIMAL (5,0), OUT
RECFOUND CHAR (1 )) LANGUAGE RPGLE DETERMINISTIC NO SQL EXTERNAL
NAME DAVNAV1/CHECKCUST PARAMETER STYLE GENERAL
Procedure PROCCHECKCUST was created in DAVNAV1.

For verifing:

SELECT * FROM SYSROUTINES or SELECT * FROM SYSPARAMS , execute the SQL and see the SCHEMA entry in the tables.

SQL Stored Procedures


SQL stored procedures are written in SQL language and this can be compiled or created using CREATE PROCEDURE or RUNSQLSTM command or iSeries Navigator

SQL SOURCE(DELETCUST):

Below example SQL source is for creating a procedure to delete the specific Customer Record.
http://publib.boulder.ibm.com/html/as400/v4r5/ic2931/info/db2/rbafymst151.htm#HDRSQLPROC




Compilation: The sql source can be compiled using the Command RUNSQLSTM


RUNSQLSTM SRCFILE(DAVNAV1/QSQLSRC) SRCMBR(DELETCUST) COMMIT(*NC) DBGVIEW(*SOURCE)

COMMIT(*NC) --> Specifies that commitment control is not used. Uncommitted changes in other jobs can be seen. If the SQL DROP SCHEMA
statement is included in the program, *NONE or *NC must be used.

DBGVIEW(*SOURCE) --> debugging with source.

CALLING SQLRPGLE PROGRAM:
--------------------------------------