After much awaiting launch of the iPad , many in the techie community have raised several comments claiming Apple's latest ipad is missing key features, functions, and hardware components. Lets see and have a review of the features that are missing which other wise will make the apple ipad a tech savvy gadget.
1.No built in Camera
Of all of the surprising omissions in the iPad, the absence of a built-in camera came as the biggest shock. With just about every mobile device incorporating some sort of camera these days, the iPad's lack of some sort of photo or video taking ability is stupefying. Granted, Apple is pushing the iPad as a web browsing, media-loving, book reading device, but given how cheap and accessible the technology is, it would have been a simple addition to the hardware.
2.No Flash Support
This is another big omission from the iPad: support for Adobe Flash. It’s bad enough on the iPhone, but imagine loading up a nice video link on the iPad only to have it… simply not play.
3.No USB Port:
Isn’t the usb point missing the point? The iPad requires a host computer; it’s more like an iPod in that sense. You can’t plug an iPod into an iPod. Just to say: the iPad is not an unhitched computer in the way a Kindle or a netbook is. Nor is it the MacCloud of my dreams, able to run off an MobileMe account.
4.No Mutitasking
From what we saw on the iPads we tested following the keynote this week, multitasking is not offered for apps on the iPad. Other than simply utilizing the iPod functionality while using other apps, you can't seem to run multiple apps at once. Apple could potentially add this feature later through a firmware update, but we wouldn't expect it for quite some time (or before the 2nd-gen iPad is announced).
5.Typing Ergonomic
The iPad will be a huge competitor for netbooks and laptops and has support for iWorks and web browsing, but its missing keyboard is one of the iPad's only disappointments. Being sort of an upgraded iPhone, an actual keyboard wasn't expected to be an inbuilt feature, but with all of the input demanding programs on the iPad, it's hard to believe that the iPad lacks a better solution than that silly keyboard dock (that isn't practical on the go).
Basic Framework of Job Control Language-JCL
My head’s spinning around the 3 JCL Statements : JOB, EXEC and DD. Could you tell me something more about them?
So, you’ve got the gist of the concept behind JCL, all the JCL that you going to write from hereon, maybe for the next 10-20 years, would be composed of three main statements :
Each of this JCL Statements have a label – a symbolic name assigned to them. Its like naming kids. Well, there could be so many boys in your area, but how do distinguish them? Of course, by their names.
In the same way, a JCL may contain a bunch of DD Statements, one for Input file, one for the output file, one for the error file. How do you tell them apart, by naming them. As a good practice, we always give names to all our JCL Statements. Names kinda help you to refer back to these statements in the future. You want to point out a particular JCL Statement to your friend, just spell out its name.
But, notice carefully, each label(name) is preceded with two slashes //. The two slashes are a JCL Statement’s signature. They indicate that the statement is a JCL Statement(one of JOB, EXEC, DD). Every JCL Statement wear the two slashes //. A naked statement without // won’t be treated as a JCL Statement.
Now, every JOB, EXEC and DD Statement has got these whole lot of parameters. What you’ll be learning throughout these tutorials is mostly the parameters. Parameters add stuff and meaning to the JCL Statement.
Now, let me give you a booster, that’s going to help you organise the way you think about this JCL.
JCL is made up of mainly JOB, EXEC and DD.
- JOB is easy to learn and use.
- EXEC is easy and fun to use.
- DD Statements take three forms
1. DD Statements to read a file.(easy)
2. DD Statements to write to the logs.(easy)
3. DD Statements to create a new file(hard!); you’d have to learn parameters such as DISP, UNIT, DCB, SPACE and several others to code this.
Have a good look at this chart :
So, you’ve got the gist of the concept behind JCL, all the JCL that you going to write from hereon, maybe for the next 10-20 years, would be composed of three main statements :
//name | JOB | parameters... |
//name | EXEC | parameters... |
//name | DD | parameters.. |
Each of this JCL Statements have a label – a symbolic name assigned to them. Its like naming kids. Well, there could be so many boys in your area, but how do distinguish them? Of course, by their names.
In the same way, a JCL may contain a bunch of DD Statements, one for Input file, one for the output file, one for the error file. How do you tell them apart, by naming them. As a good practice, we always give names to all our JCL Statements. Names kinda help you to refer back to these statements in the future. You want to point out a particular JCL Statement to your friend, just spell out its name.
But, notice carefully, each label(name) is preceded with two slashes //. The two slashes are a JCL Statement’s signature. They indicate that the statement is a JCL Statement(one of JOB, EXEC, DD). Every JCL Statement wear the two slashes //. A naked statement without // won’t be treated as a JCL Statement.
Now, every JOB, EXEC and DD Statement has got these whole lot of parameters. What you’ll be learning throughout these tutorials is mostly the parameters. Parameters add stuff and meaning to the JCL Statement.
Now, let me give you a booster, that’s going to help you organise the way you think about this JCL.
JCL is made up of mainly JOB, EXEC and DD.
- JOB is easy to learn and use.
- EXEC is easy and fun to use.
- DD Statements take three forms
1. DD Statements to read a file.(easy)
2. DD Statements to write to the logs.(easy)
3. DD Statements to create a new file(hard!); you’d have to learn parameters such as DISP, UNIT, DCB, SPACE and several others to code this.
Have a good look at this chart :
Subscribe to:
Posts (Atom)