Simulation system language
General Purpose Simulation System (GPSS) is a simulation language used for discrete-event simulations. It is especially useful in the modelling of queuing systems, with many statistics being collected automatically. The typical simulation consists of "Transactions" being generated in the system (usually at a certain interval), performing a defined set of rules (like use a resource, wait, transfer), and being removed from the simulation.
History.
GPSS was developed in the 1960s by Geoffrey Gordon, an employee of IBM's Advanced Systems Development Division (ASDD). This division was heavily involved with research into the design of teleprocessing systems, trying to achieve an economic balance of the use of computer resources and shared lines between server terminals. The simulation system, then known as the Gordon Simulator, became very popular in the study of teleprocessing systems within ASDD. It subsequently was fixed and documented on October 25, 1960 in an internal IBM memorandum. Between the winter and summer of 1961, a group of three programmers (including Gordon) rewrote the simulation system with a new algorithm and new block types. It was officially released as a supported IBM-label program on September 27, 1961 with 25 block types. At this point, Gordon stopped working on the simulation system.
In 1963, GPSS II was released with 32 block types. It introduced system numerical attributes, which allowed tracking the current content of a "Storage", the length of a "Queue", or the current clock time.
In 1965, GPSS III was released. It was made available for IBM Systems 7090/94 and 7040/44.
In 1967, GPSS/360 was released to run on the newly released System 360.
In 1970, GPSS V was released with 49 block types.
In the 1980s, GPSS/VAC and GPSS/PC were released. These appear to be the last official IBM-label releases before the language became unlicensed.
Subsequently, there were releases for IBM 360, Univac 1108, and CDC.
Over time, other implementations were developed for systems including DEC's VAX, a specialized APL version for large-scale Univac systems, and Macintosh.
In 2001, the Windows program GPSS World was released with new features to GPSS. It includes scripting with PLUS (a Pascal-like language), graphical system state displays, graphing, and optimization experiments.
In 2009, a graphical Java-based tool called JGPSS (Java General Purpose Simulation System) was developed to teach the GPSS simulation language.
Description.
A GPSS simulation is written in an Assembly-style "block diagram language" with many different single-purpose commands ("Blocks") to control the flow of a "Transaction", statistics collection, and variables. 
Simulations have "Transaction" entry points through the codice_1 command, such as a customer walking into a store. Then, actions are performed through claiming "Facilities"/"Storage" (like a cashier), waiting, saving statistics, etc. Finally, the simulated transaction exits the simulation through the codice_2 command. Each command verb is referred to as a "control".
Blocks can be facility-oriented (such as machines in a job shop) or transaction-oriented (such parts of work-in-process, signals in electronic components or documents in a bureaucratic procedure). GPSS automatically keep track of statistics for display on a report. 
Entities can be broadly classified in Resources, Computational entities and Statistical entities. Resources, like "Facilities" and "Storages" represent limited capacity resources. Computational entities, like "Ampervariables" (variables), "Functions" and random generators are used to represent the state of Transactions or elements of their environment. Statistical entities, like "Queues" or "Tables" (histograms) collect statistical information of interest.
Basic Transaction commands.
Transactions can :
Along with these main tasks, they can also hold parameters with the ASSIGN command. Transactions are implicitly sectioned off in the code.
There can be multiple transactions in the code that happen at once. A transaction starts with GENERATE and ends with TERMINATE. The code inbetween could potentially be shared between multiple transactions by means of the TRANSFER command, but besides that your transaction lifecycles will be separated. It helps to add whitespace between lines of action of one transaction versus another.
GENERATE.
 GENERATE 0.1
Transaction generated every 0.1 time unit.
 GENERATE 15,4
Transaction is generation every 15 time units, plus or minus 4 time units.
GENERATE
ADVANCE.
To have a transaction wait, use the ADVANCE command. It has similar arguments to GENERATE.
 ADVANCE 10,6
Transaction waits 10+-6 seconds.
ADVANCE
SEIZE, RELEASE (Facilities).
To use a Facility, which only allows one use at a time, use the SEIZE command. To stop using it, use the RELEASE command.
 GENERATE 30,5 ; Generate a customer every 30+-5 time units
 SEIZE Barber ; Use a facility
 ADVANCE 15,4 ; Wait 15+-4 time units
 RELEASE Barber ; Stop using the facility
 TERMINATE 1 ; Leave the barber shop
If you want more than one use at a time, use Storage.
SEIZE
RELEASE
ENTER, LEAVE (Storages).
 Seating STORAGE 100 ; 100 people allowed in lounge seating
 GENERATE 10,5 ; Generate a person every 10+-5 time units
 ENTER Seating,1 ; Person sits down
 ADVANCE 15,4 ; Wait 15+-4 time units
 LEAVE Barber,1 ; Person stops sitting
 TERMINATE 1 ; Exit the seating area
This way, multiple people can sit in the Seating at once. If this was a "Facility" (using SEIZE/RELEASE), it would block others who tried to use the resource.
The ENTER command takes the storage reference as Argument A and the amount to reserve with Argument B. The LEAVE command's arguments are the same.
ENTER
LEAVE
TERMINATE.
To remove the transaction, use TERMINATE.
The optional argument decrements the completion counter, which is a variable that is chosen by the user when running the simulation. Say you wanted to test 100 customers: you would start the execution of your simulation with codice_3. codice_4 at the end of each transaction would decrement initial value 100 by 1 (99, 98, 97 ...) until it reached zero. At this point, the simulation stops and results are returned. If you omit the argument in TERMINATE, it will be assumed to be 0. This means your simulation will run forever (unless, of course, you have another TERMINATE that does decrement this counter.
TERMINATE
Timer.
To have your program run for a predetermined time, make sure none of your TERMINATES decrement the counter and include a section like this:
 GENERATE ; Generate one transaction
 ADVANCE 100 ; Run for 100 time units
 TERMINATE 1 ; End
Then run your program with START 1. It will run for 100 time units.
ASSIGN (Parameter "Metadata").
Use the ASSIGN control block to assign a value to a transaction parameter. Called with Pj (j=parameter number)
 ASSIGN 2,V$Orderqty     ;Parameter 2=Order quantity
 Custwait    ADVANCE 5               ;Lead time is 5 days
 ENTER Stock,P2          ;Stock increases by P2
ASSIGN : ASSIGN Blocks are used to place or modify a value in a Transaction Parameter.
Examples.
Barber Shop.
The following example, taken from "Simulation using GPSS", is the "Hello world!" of GPSS and will illustrate the main concepts.
The aim is to simulate one day of operation of a barber shop. Customers arrive in a random constant flow, enter the shop, queue if the barber is busy, get their hair cut on a first-come first-served basis, and then leave the shop. We wish to know the average and maximum waiting line, as well as the number of customers.
The "program" is comprised between the codice_5 and codice_6 statements, and is divided into "model segments" and "control cards".
The first segment models customers. The codice_1 block creates a flow of Transactions and schedules them to enter the model with an inter-arrival time uniformly distributed over the range 18±6. It is the programmer's responsibility to interpret these transaction as customers and to understand that the time is to be counted in minutes. The Transactions start their existence in the codice_1 block and progress from Block to Block, according to certain rules, until they reach a codice_2 which remove them from the model.
Normally transactions progress from one block to the next one, so the customer transactions will leave the codice_1 block to enter the codice_11 block. This block simulates a waiting line, and collects statistics accordingly. In the example, it materialize a line of chairs and, at the end of the simulation, we will know, among other things, the maximum queue size (how many chairs are needed) and the average waiting time. The codice_12 block requires the name of the queue as a parameter, because more than one queue may exist in the model. Each one is associated with a codice_13 block, which is triggered when the transaction leaves the queue. GPSS remembers which transactions are in the queue, so that it possible to know the average time spent, and to check that no buggy transaction is leaving a queue without previously entering in it.
After the codice_14 block, the transaction will try to proceed to the codice_15 block, a block simulating the capture of the "Facility" named Joe. Facilities model single servers of capacity one. If the facility is busy, the codice_16 will deny the attempting transaction the right to enter. In the example, the customer will wait in the codice_12 block. If it is free, or as soon as it becomes available, the transaction will be allowed to capture the facility, mark it as busy to others transactions and start to count the service time and other statistics, until the same transaction passes the corresponding codice_18 block.
The codice_16 / codice_20 pairs are linked by the facility name, because many independent facilities may exist in the model. They can model operators, like a barber, a repairman, an agent, but also pieces of equipment, like a crane, a gas station, an authorization document, etc., in fact anything with capacity one. To simulate multiple parallel servers, like a team of five barbers, or an oven with a capacity of 10, GPSS uses entities named codice_21s.
After a customer seizes Joe, she proceeds to the next statement which is codice_22, whose task is to freeze the entity for a prescribed length of time, here a random number picked between 16-4=12 and 16+4=20mn. Other service time distributions are available through GPSS codice_23 (a somehow different notion than function in other programming languages). During that time, other transactions will be allowed to move through the model, blocking some other facilities that may exist in the model, but not Joe because this facility is busy with the frozen customer. After the prescribed time, the customer will wake up, proceed to the next statement, which will free Joe, and codice_2.
Then the next transaction on the previous block, that is a customer sitting on a chair, will be able to codice_15. To select the "next" transaction, GPSS uses the first-come first-served basis, with priority. Other selection policies can be programmed by direct manipulation of the "future event chain" entity.
In parallel to this first segment, simulating the customer behavior, a second model segment simulates the end of the day. At time 480mn = 8h an entity is codice_1d, which will codice_2 on the next block. This time, the codice_2 as a parameter of 1, meaning a special counter is decreased by 1. When that counter reaches 0, the program stops and the output is printed. This special counter is set up with the codice_29 statement. In the example, it is set to one, thus the simulation will finish after one run of 480 mn in simulated time.
The output contains:
It indicates that Joe was busy 86.0% of the time, gave a hair cut to 26 customers and that hair cut took 15.88 minutes on the average. Incidentally, Joe was cutting the hair of customer number 26 when the simulation was closed. No programming provisions were taken for the barber to finish the hair cut before closing the shop.
It indicates also that a maximum of 1 customer was observed waiting his turn, in fact the number of waiting customer was on the average 0.160. A total of 27 customers did enter the queue, so that customer number 27 was still sitting, waiting his turn, when Joe closed the shop. Out of these 27 customers, 12 were served without having to wait. In fact, the queue was empty 44.4% of the time. The average waiting time was 2.851 min, and the average waiting time for the 15=27-12 customers who did really wait was 5.133 min.
Haircuts.
 * Pg 108 Q 18
 * A one-chair unisex hair shop has arrivals at the rate of one every 20+-15 minutes.
 * One-half of the arriving customers want a dry cuts, 30% want a style, and 20% 
 * want a trim only. A dry cut takes 15+-5 minutes, a style cut takes 25+-10 minutes,
 * and a trim takes 10+-3 minutes. Simulate 50 customers coming through the hair
 * shop. Compare the given proportion of service