Oh I'm sorry. I understand now.

I see that you want to tokenize the actual control cards to determine their size, etc and then collect additional information for the actual control-cards (such as their data sections and the attributes for the data sections).

I thought you needed an easier means of grouping the data, but I misunderstood at first.

It's still possible to use my first suggestion, however you will need to determine what defines a control card. For example, will all sizes of user programs be 16+ in hexadecimal? Is the data reliably grouped in the .txt file?

I can see of another way of this being done, but I need more information about how the information is organized in the .txt file (consistency, etc) and if there is a specific format for user programs (do they always have a number at the end of their name to identify them?), and do Data section always start with the word Data?

Yes thats what i've been trying to do. And now that i've gone deeper into the Operating system structure, i need to interconnect these 3 classes am working on. PCB, Hardware Layer and Loader. The PCB takes and stores process info(control card) and is stored in a data structure of choice. While the Hardware layer, defines the memory and disk block and the loader reads in the user program and strips of the control card then stores the process data in disk/memory.

I'll just attached everything that i've done so far and a sample program text file we'll be getting so u'll know the format.

I havn't done the short term and long term scheduler yet or the CPU...but i wanted to finish this before the weekened is over with and start on those as soon as possible. Thanks again for seeing through this with me.

Crap am not sure if am allowed to this do but my thread is getting lost amongst other (solved) threads.