http://www.localphone.com/ways_to_connect/incoming_calls
http://www.trackitt.com/uk-discussion-forums/tier-1-general/259403209/how-to-get-uk-sim-in-india
http://techshali.com/get-a-free-uk-number-and-forward-it-to-phone-with-free-incoming/
http://www.lonelyplanet.com/thorntree/thread.jspa?threadID=1653900
http://www.qxcall.co.uk/call/international.php?country=india
http://www.vtelix.com/Incoming.html
http://www.jetnumbers.com/buy-virtual-number2&from=header
https://www.future-nine.com/A2BCustomer_UI/signup/?tariff=3
Tuesday, May 10, 2011
NATURAL ADABAS : Refresher NATURAL 01 - Data Areas
Natural offers two ways of programming:
Reporting Mode:
Reporting mode is only useful for the creation of adhoc reports and small programs which do not involve
complex data and/or programming constructs.
Please note that certain Natural statements are available only in reporting mode, whereas others have a
specific structure when used in reporting mode.The statements END, LOOP (or CLOSE LOOP) or SORT may be used to close a processing loop.
The LOOP statement can be used to close more than one loop, and the END statement can be used to close
all active loops. These possibilities of closing several loops with a single statement constitute a basic
difference to structured mode.
A SORT statement closes all processing loops and initiates another processing loop.
Structured Mode
Structured mode is intended for the implementation of complex applications with a clear and well-defined
program structure.As all fields to be used in a program have to be defined in one central location (instead of being
scattered all over the program, as is possible in reporting mode), overall control of the data used is
much easier.
Structured Mode:GLOBALS SM=ON
Reporting Mode:GLOBALS SM=OFF
Data Areas
Local Data Area:
You can define local data within a program.
You can define local data outside a program in a separate Natural programming object.
Global Data Area
When you build an application where multiple Natural programming objects reference a GDA, remember
that modifications to the data element definitions in the GDA affect all Natural programming objects that
reference that data area. Therefore these objects must be recompiled by using the CATALOG or STOW
command after the GDA has been modified.
Each Natural programming object can reference only one GDA; that is, a DEFINE
DATA statement must not contain more than one GLOBAL clause.
Creating and Deleting GDA Instances
The first instance of a GDA is created and initialized at runtime when the first Natural programming
object that references it starts to execute.
Once a GDA instance has been created, the data values it contains can be shared by all Natural
programming objects that reference this GDA (DEFINE DATA GLOBAL statement) and that are invoked
by a PERFORM, INPUT or FETCH statement. All objects that share a GDA instance are operating on the
same data elements.
A new GDA instance is created if the following applies:
A subprogram that references a GDA (any GDA) is invoked with a CALLNAT statement.
A subprogram that does not reference a GDA invokes a programming object that references a GDA
(any GDA).
If a new instance of a GDA is created, the current GDA instance is suspended and the data values it
contains are stacked. The subprogram then references the data values in the newly created GDA instance.
The data values in the suspended GDA instance or instances is inaccessible. A programming object only
refers to one GDA instance and cannot access any previous GDA instances. A GDA data element can only
be passed to a subprogram by defining the element as a parameter in the CALLNAT statement.
When the subprogram returns to the invoking programming object, the GDA instance it references is
deleted and the GDA instance suspended previously is resumed with its data values.a subprogram referencing a GDA cannot share the data values in a GDA
instance referenced by the invoking program. A subprogram that references the same GDA as the
invoking program creates a new instance of this GDA. The data elements defined in a GDA that is
referenced by a subprogram can, however, be shared by a subroutine or a helproutine invoked by the
subprogram.
A GDA instance and its contents is deleted if any of the following applies:
The next LOGON is performed.
Another GDA is referenced on the same level (levels are described later in this section).
A RELEASE VARIABLES statement is executed. In this case, the data values in a GDA instance are
reset either when a program at the level 1 finishes executing, or if the program invokes another
program via a FETCH or RUN statement.
You cannot use the FETCH RETURN statement to invoke another program that references a different
GDA.
Parameter Data Area
A subprogram is invoked with a CALLNAT statement. With the CALLNAT statement, parameters can be passed from the invoking object to the subprogram.
Reporting Mode:
Reporting mode is only useful for the creation of adhoc reports and small programs which do not involve
complex data and/or programming constructs.
Please note that certain Natural statements are available only in reporting mode, whereas others have a
specific structure when used in reporting mode.The statements END, LOOP (or CLOSE LOOP) or SORT may be used to close a processing loop.
The LOOP statement can be used to close more than one loop, and the END statement can be used to close
all active loops. These possibilities of closing several loops with a single statement constitute a basic
difference to structured mode.
A SORT statement closes all processing loops and initiates another processing loop.
Structured Mode
Structured mode is intended for the implementation of complex applications with a clear and well-defined
program structure.As all fields to be used in a program have to be defined in one central location (instead of being
scattered all over the program, as is possible in reporting mode), overall control of the data used is
much easier.
Structured Mode:GLOBALS SM=ON
Reporting Mode:GLOBALS SM=OFF
Data Areas
Local Data Area:
You can define local data within a program.
You can define local data outside a program in a separate Natural programming object.
Global Data Area
When you build an application where multiple Natural programming objects reference a GDA, remember
that modifications to the data element definitions in the GDA affect all Natural programming objects that
reference that data area. Therefore these objects must be recompiled by using the CATALOG or STOW
command after the GDA has been modified.
Each Natural programming object can reference only one GDA; that is, a DEFINE
DATA statement must not contain more than one GLOBAL clause.
Creating and Deleting GDA Instances
The first instance of a GDA is created and initialized at runtime when the first Natural programming
object that references it starts to execute.
Once a GDA instance has been created, the data values it contains can be shared by all Natural
programming objects that reference this GDA (DEFINE DATA GLOBAL statement) and that are invoked
by a PERFORM, INPUT or FETCH statement. All objects that share a GDA instance are operating on the
same data elements.
A new GDA instance is created if the following applies:
A subprogram that references a GDA (any GDA) is invoked with a CALLNAT statement.
A subprogram that does not reference a GDA invokes a programming object that references a GDA
(any GDA).
If a new instance of a GDA is created, the current GDA instance is suspended and the data values it
contains are stacked. The subprogram then references the data values in the newly created GDA instance.
The data values in the suspended GDA instance or instances is inaccessible. A programming object only
refers to one GDA instance and cannot access any previous GDA instances. A GDA data element can only
be passed to a subprogram by defining the element as a parameter in the CALLNAT statement.
When the subprogram returns to the invoking programming object, the GDA instance it references is
deleted and the GDA instance suspended previously is resumed with its data values.a subprogram referencing a GDA cannot share the data values in a GDA
instance referenced by the invoking program. A subprogram that references the same GDA as the
invoking program creates a new instance of this GDA. The data elements defined in a GDA that is
referenced by a subprogram can, however, be shared by a subroutine or a helproutine invoked by the
subprogram.
A GDA instance and its contents is deleted if any of the following applies:
The next LOGON is performed.
Another GDA is referenced on the same level (levels are described later in this section).
A RELEASE VARIABLES statement is executed. In this case, the data values in a GDA instance are
reset either when a program at the level 1 finishes executing, or if the program invokes another
program via a FETCH or RUN statement.
You cannot use the FETCH RETURN statement to invoke another program that references a different
GDA.
Parameter Data Area
A subprogram is invoked with a CALLNAT statement. With the CALLNAT statement, parameters can be passed from the invoking object to the subprogram.
Subscribe to:
Posts (Atom)