Technology Questions

to access non-public data outside class getter methods be defined but we cannot define a  method inside interface we can declared a method inside interface.

Server control events can be handled inside a server itself

Parallel/audit testing is testing where the user reconciles the output of the new system to the output of the current system to verify the new system performs the operations correctly. Let us say, for example, the currently software is in the mainframe system which calculates the interest rate. The company wants to change this mainframe system to web-based application. While testing the new web based application, we need to verify that the web-based application calculates the same interest rate. This is parallel testing.

Events keywords in Reports are:

For Classical Reports,

1.Initialization

2. At line-selection 

3. Start-of-selection 

4.Top-of-page 

5. At user-command 

6.End-of-selection 

7. End-of-page 

8.At Pfn

For Interactive Reports,

9.At line-selection 

10. Top-of-page during line selection

For LDB (Logical DataBase) Reports,

10. get 

11.put 

12. get table 

Inside an interface every method will be by default abstract and public

An in-stream PROC is defined right in the jcl stream and doesn't reside in the proclib. This is an older technique associated with punched cards but it is still in use with setup and installation programs from vendors.

for the in-line perform instead of:

perform add-paragraph until switch = 'y'

you can code

perform until switch = 'y'

body of code

end-perform

body of code is the code from add-paragraph appearing in-line (ie right in the perform) instead of in a separate paragraph (out of line code)

Both GET and POST are used to collect data from a form. However, when security is desired $_POST should be used. When the $_ POST variable is used, all variables used are NOT displayed in the URL. Also, they have no restrictions to the length of the variables. GET should be used when the interaction with the form is more like a question. For e.g. firing a query etc. POST should be used more often when the interaction is more like an order or the interaction changes the state of the resource.

POST example:

<form action="sample.php" method="post">

Name: <input type="text" name="name" />

Age: <input type="text" name="age" />

<input type="submit" />

</form>

On clicking submit the URL resembles to: https://www.mysamplesite.com/sample.php

The sample.php file can be used for catching the form data using $_POST 

Hello <?php echo $_POST["name"]; ?>.<br />

You are <?php echo $_POST["age"]; ?> years old!

GET EXAMPLE

<form action="sample.php" method="get">

Name: <input type="text" name="name" />

Age: <input type="text" name="age" />

<input type="submit" />

</form>

On clicking submit the URL resembles to : https://www.mysamplesite.com/sample.php?name=jim&age=37

The sample.php file can be used for catching the form data using $_GET 

Hello <?php echo $_GET["name"]; ?>.<br />

You are <?php echo $_GET["age"]; ?> years old!