virtual storage/storage device



Support for OS/VS COBOL, VS COBOL II, COBOL for OS/390 & VM and Enterprise COBOL for z/OS

virtual storage/storage device

Postby raju181 » Wed Mar 16, 2011 2:36 pm

Wt z meant by virtual storage & storage device ?
raju181
 
Posts: 4
Joined: Mon Mar 07, 2011 8:23 pm
Has thanked: 0 time
Been thanked: 0 time

Re: virtual storage/storage device

 

Re: virtual storage/storage device

Postby Robert Sample » Wed Mar 16, 2011 2:52 pm

What do you mean by
Wt z meant by virtual storage & storage device ?
This is not some IM or Twitter site -- this is a site for mainframe students and beginners. Since a big part of IT is communication, people posting on this forum are expected to use standard English, and it is up to the person writing the post to ensure that clear, precise communication is achieved.

Google is your friend. Googling virtual storage returns 7,140,000 hits -- some of which on the very first page give the IBM definition. Googling storage device returns 18,700,000 hits -- and again the very first page has links to the answer you asked for. So the question really is, do we need to teach you how to use Google?
Robert Sample
Global moderator
 
Posts: 3367
Joined: Sat Dec 19, 2009 8:32 pm
Location: East Dubuque, Illinois
Has thanked: 1 time
Been thanked: 222 times

Re: virtual storage/storage device

Postby NicC » Wed Mar 16, 2011 4:42 pm

Or even - 'do we need to teach you how to read the forum rules'?
And what is 'Wt z'?
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: virtual storage/storage device

Postby enrico-sorichetti » Wed Mar 16, 2011 4:51 pm

And what is 'Wt z'?


I just could not resist

...
do forever
   what is 'Wt z'
   what is
   what is what
end


same silliness as
where are You going
to see a movie
what movie
quo vadis
what does it mean
where are You going
...
...
...
Last edited by enrico-sorichetti on Wed Mar 16, 2011 4:55 pm, edited 1 time in total.
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
enrico-sorichetti
Global moderator
 
Posts: 2643
Joined: Fri Apr 18, 2008 11:25 pm
Has thanked: 0 time
Been thanked: 130 times

Re: virtual storage/storage device

Postby NicC » Wed Mar 16, 2011 4:54 pm

Did you test that code before posting?? :lol: :lol:
The problem I have is that people can explain things quickly but I can only comprehend slowly.
Regards
Nic
NicC
Global moderator
 
Posts: 2690
Joined: Sun Jul 04, 2010 12:13 am
Location: Pushing up the daisys (almost)
Has thanked: 4 times
Been thanked: 105 times

Re: virtual storage/storage device

Postby enrico-sorichetti » Wed Mar 16, 2011 4:56 pm

the silliness of these puns is that at each iteration the roles switch :D
cheers
enrico
When I tell somebody to RTFM or STFW I usually have the page open in another tab/window of my browser,
so that I am sure that the information requested can be reached with a very small effort
enrico-sorichetti
Global moderator
 
Posts: 2643
Joined: Fri Apr 18, 2008 11:25 pm
Has thanked: 0 time
Been thanked: 130 times

Re: virtual storage/storage device

Postby Adam_rock » Tue Nov 15, 2011 2:00 am

Hello friends,

I am paying no attention to the purpose of the forum. My nonsense post has been deleted.

Thanks,
Adam
Adam_rock
 
Posts: 1
Joined: Tue Nov 15, 2011 1:58 am
Has thanked: 0 time
Been thanked: 0 time

Re: virtual storage/storage device

Postby dick scherrer » Tue Nov 15, 2011 2:19 am

Adam,

One more unacceptable post and you will no longer be permitted to post. . .

d
User avatar
dick scherrer
Global moderator
 
Posts: 6304
Joined: Sat Jun 09, 2007 8:58 am
Has thanked: 3 times
Been thanked: 91 times

Re: virtual storage/storage device

Postby BillW » Tue Nov 15, 2011 5:57 am

Maybe it is better to consider first real storage before we think about virtual storage. In the computer system, there are several major components, the cpu, real memory where programs, both instructions and data are stored and i/o channels to get the programs and data to and from the storage devices which are primarily consist of DASD devices (hard disks, drives). The thing to remember here is that the hard drives will keep the data when the power is shut off where most (but not all) real memory will not.

At some point in the early 70s it was recognized that most programs have a locality of reference pattern where the probability that the next instruction or data element was "close" (where we will say close is a close address (neighbor if you will)) to the last instruction or data. It can also be noted that there are some sections of the program that may be used infrequently or not at all during this execution of the program. To that end, virtual storage was developed to allow the programmer to use more storage then was physically present in the computer (remember the real memory of the systems was many thousands of times more expensive then today and many times limited as to the amount of memory one could put into the system).

So, how does work (well, I will try to give you an accurate picture but skipping lots of details). Lets say the supervisor code (system loader) is loading a program in a virtual storage environment. The program is loaded using the virtual address's but those addresses are "translated" by hardware (this translation is performed by using lookup tables indexed by portions of the virtual address and maintained by the system supervisory code). Lets first say that the virtual address space and the real memory of the system are both divided into 4096 byte "pages" and a group of contiguous pages are called segments (and say 16 pages for a 64k segment. In reality, there are options to specify segment size). But, the system can map the virtual address to the real address, only when the contents of that virtual page are in real memory. Another possibility is that the contents of that page are currently not in real memory but rather out on the DASD page file. In which case, the system will indicate a program check with a page fault indication to the supervisory program (of course at this point, the supervisory will perform the necessary work to bring the page contents into real memory (some where) and point the page table entry (for this given virtual address) to the real memory just filled in from DASD and restart the program to retry the instruction that caused the page fault in the first place. Another nice thing about virtual storage is that although the program instructions/data MUST be in real memory before the CPU can use it, the program (being broken up into 4096 byte chunks) can place contiguous virtual storage pages into dis-contiguous 4096 byte pages (also remember that the 4096 pages are on 4096 byte boundary, which makes real storage management more flexible).

OK, so this may or may not be what you are looking for. I would recommending finding some reading on the subject. Preferably some that try to explain it simply at first and get more into details a little later in the book. (there may be a redbook on this subject, get an older one first, as the paging system was simpler in 370 than z-OS.

Good Luck.
BillW
 
Posts: 20
Joined: Thu Nov 10, 2011 8:21 am
Has thanked: 0 time
Been thanked: 3 times


Return to IBM Cobol

 


  • Related topics
    Replies
    Views
    Last post