Custom Query (17 matches)

gtss
GTSS 4JS3 (4.0)
*status


channel 0400 ts0
user status on may 16,1925 at 14:13:09  log-on at 14:13:03
proc time used  0.05 sec., 0 file i/o   char key i/o
list of open files: none

*

Year is displayed as "1925" insted of "2025".

I am unsure if this is merely a cosmetic problem or indicative of of deeper Y2K issues in the GCOS TSS simulation.

Now that the GCOS Daemon is working, it would be helpful to have operator support from the console in starting and maintaining it.

For example, "x io" and "x io1" prepare the printers, punches, etc. for use. It would be nice to have a "x gcos" that would login the GCOS daemon.

In a similar fashion, "x read_cards" starts a read on the card reader, "x gcos_read_cards" could attach and start the GCOS Daemon card reading.

The GCOS daemon is installed but not registered or configured. It would save some time and the need for following the installation documentation to setup the daemon with an empty user table.

See AN05-02A, Appendix A:

Creating the GCOS User Table (A-5) Initializing the User Table (A-5) Installing the GCOS SysDaemon (A-6 — A-7)

gtss GTSS 4JS3 (4.0) *old MRGD <50>FILE MRGD -- NONEXISTENT *bye r 18:50 0.280 7

gtss GTSS 4JS3 (4.0) *system basic *10 print "Multics Rulez, GCOS Droolz" *run

Multics Rulez, GCOS Droolz

ready *save NRGD

Error: conversion condition by any_to_any_$formline_|6213 (>system_library_1>bound_library_wired_) onsource = "chain", onchar = "c" Invalid character follows a numeric field. system handler for error returns to command level r 18:50 0.542 80 level 2

probe Condition conversion raised at formline_|53565 (level 16). stack long

23 command_processor_|2101 (>sl1>bound_multics_bce_|2101) (pl1) 22 release_stack|554 (>sss>bound_command_loop_|34522) (pl1) 21 unclaimed_signal|177 (>sss>bound_command_loop_|35521) (pl1) 20 wall|2724 (>sl1>bound_error_handlers_|2724) (pl1) 19 any_other.2|426 (>sss>bound_process_init_|426) (pl1) 18 wall|2671 (>sl1>bound_error_handlers_|2671) (pl1) error 17 any_other.2|426 (>sss>bound_process_init_|426) (pl1) 16 formline_|50471 (>sl1>bound_library_wired_|53565) conversion 15 general_rs|1147 (>sl1>bound_library_wired_|16621) (pl1) 14 com_err_|573 (>sl1>bound_library_1_|26443) (pl1) 13 open|6035 (>unb>bound_gcos_tss_|252745) (pl1) 12 gtss_ios_open_|1226 (>unb>bound_gcos_tss_|244306) (pl1) 11 gtss_filact_funct04_|1032 (>unb>bound_gcos_tss_|204150) (pl1) 10 gtss_drl_filact_|2247 (>unb>bound_gcos_tss_|106413) (pl1)

9 gtss_derail_processor_|2570 (>unb>bound_gcos_tss_|57432) (pl1) 8 <<NO ENTRYPOINT>>|2753 (>pdd>!BMBDnFQbBBBBBB>!BBBKMPLWMpZgNM.temp.0324|2753) (Other) derail 7 gtss_run_subsystem_|1503 (>unb>bound_gcos_tss_|24605) (pl1) 6 exec_primitive|3673 (>unb>bound_gcos_tss_|21127) (pl1) 5 gtss_interp_prim_|2371 (>unb>bound_gcos_tss_|17625) (pl1) 4 gtss|1625 (>unb>bound_gcos_tss_|7563) (pl1) 3 command_processor_|2101 (>sl1>bound_multics_bce_|2101) (pl1) 2 listen_|554 (>sss>bound_command_loop_|34522) (pl1) 1 initialize_process_|704 (>sss>bound_process_init_|704) (pl1)

qedx r gtss_verify_access_.pl1 $

end;\000

This is a probably an artifact of the ACTC recovery.

The DPS/Level 86 & DPS 8M Multics Processor Manual (AL39-01C) have incomplete descriptions of the RPD, RPL, and RPT instructions. The missing details may be found in the [DPS 8 and DPS 88 Assembly Instructions (DH03-01) | ​http://www.bitsavers.org/pdf/honeywell/series60level66/DH02-01_dps8asm_Jun84.pdf] manual.

The missing information describes how ALM instructions set the various fields in these instructions. The more-complete GCOS manual provides these details. I have verified that these specification details are supported by the equivalent ALM instructions.

The remaining discussion focuses on information missing from the RPD instruction description. Similar information should be provided (based upon descriptions in DH03-01) for the RPL and RPT instructions.

Pertinent missing information for RPD refers to a diagram for the RPD instruction word: Figure 4-9. Repeat Double (rpd) Instruction Word Format in AL39-01.

The DPS/Level 86 & DPS 8M Multics Processor Manual (AL39-01C) have incomplete descriptions of the RPD, RPL, and RPT instructions. The missing details may be found in the [DPS 8 and DPS 88 Assembly Instructions (DH03-01) | ​http://www.bitsavers.org/pdf/honeywell/series60level66/DH02-01_dps8asm_Jun84.pdf] manual.

The missing information describes how ALM instructions set the various fields in these instructions. The more-complete GCOS manual provides these details. I have verified that these specification details are supported by the equivalent ALM instructions.

The remaining discussion focuses on information missing from the RPD instruction description. Similar information should be provided (based upon descriptions in DH03-01) for the RPL and RPT instructions.

Pertinent missing information for RPD refers to a diagram for the RPD instruction word: Figure 4-9. Repeat Double (rpd) Instruction Word Format in AL39-01.

The DPS/Level 86 & DPS 8M Multics Processor Manual (AL39-01C) has incomplete descriptions of the RPD, RPL, and RPT instructions. The missing details may be found in the [DPS 8 and DPS 88 Assembly Instructions (DH03-01) | ​http://www.bitsavers.org/pdf/honeywell/series60level66/DH02-01_dps8asm_Jun84.pdf] manual.

The missing information describes how ALM instructions set the various fields in these instructions. The more-complete GCOS manual provides these details. I have verified that these specification details are supported by the equivalent ALM instructions.

Compare AL39-01C description of RPD with the DH-03 description (page 7-333 and following). The missing information is in the Coding Format section of the DH-03 description. Items covered:

• How to set the TALLY, A, B, C fields of the instruction using RPD, RPDX, RPDA and RPDB instruction mnemonics
• How to specify the Term Cond. field using either instruction mnemonics or an octal value.

Similar information is missing from the AL39 descriptions of the RPT and RPL instructions as compared to that provided in DH-03.

gtss
GTSS 4JS3 (4.0)
*jovial
10 PROC FOO;
20 END
end
COMMAND UNKNOWN
*run
SSA_buf_ptr -> 362|374
File list ptr -> 362|7456
Urgency 163840 (500000)
Snumb 0003t
Activity name jovial
IO time limit 0.
Job time limit  1.6666666667e-2
Job io time limit 0.
PSW 010004000000
Geload limit 060000070000
$ ident	!!!!!!anthony     00000000000000100[000000000000000000!!!!!!
$ comment 000000000000000000000000000000000000000000000000000000000000

file list .. 10 entries
syslib L*
altlib *L
*src S*
r* R*
h* H*
p* P*
b* B*
*1 *1
*2 *2
*j *J
 *SRT  0003t-01  @1043.3  jovial  (  5)
m4/n4-i/o lim. call/save
 *ABT  0003t-01  @1043.3  m4/n4-i/o lim. call/save

GCOS sysout files NOT queued for daemon output:
>user_dir_dir>Ring0>Anthony>gtss_task.sysprint.list

Error:  Segment-fault error by gtss_ios_io_$|1502
(>system_library_unbundled>bound_gcos_tss_)
referencing 424|0
There was an attempt to use an invalid segment number.
r 10:43 1.169 31 level 2

gcos_gein_pass1_ makes a pass over the deck to find cards, such as the EXECUTE card. It extracts the card type, and compares it to a table of lowercard card names. It is perfectly legitimate to use uppercase names for the cards, as shown in gcos_gein_, the main processor of gcos card decks, which *does* lowercase the card type before comparisons.

As a result, the first pass through the card deck doesn't find any EXECUTE cards, and consequently, sets switch 5 OFF. Any compilation activity leaves switch 5 off, and consequently, any EXECUTE activity is logically removed from the deck.

Changing gcos_gein_pass1_ to lowercase card types before comparing them causes the execution of compiled programs to work.

The GCOS Batch Simulator is imposing a restriction that did not exist in real GCOS: It is insisting that the $SNUMB card be immediately followed by a $IDENT card.

When GTSS submits a job via CARDIN, it has the first 4 cards as: $SNUMB $COMMENT $USERID $IDENT

This card sequence is valid but GCOS batch rejects the job for the above reason. Since modification of GTSS is not possible, the GCOS batch system should be modified to allow $COMMENT and $USERID cards between the $SNUMB and $IDENT cards. The GCOS batch system ignores both the $COMMENT and $USERID (other than including them in the sysout listing of the JCL) so this should not present an issue.

Create 355sim.deck with the following content:

$      SNUMB   0001T
$      IDENT
$      355MAP  NDECK,COPY
       ABS
       TTL     TEST PROGRAM
       DCARD   3,*
       PMC     ON
       SYSTM
       ORG     1024
START  LDA     TEMP-*
       STA     NUMBER-*
       STOP
TEMP   BSS     1
NUMBER BSS     1
       END     START
***EOF

Submit the deck with the command:

gcos 355sim.deck

Examine the job output:

pr 355sim.deck

Note that lines 4,5 and 6 have acquired leading asterisks:

                                      3        DCARD   3,*
                                      4 *      PMC     ON
                                      5 *      SYSTM
                                      6 *      ORG     1024
       00000  0 07 003        3       7 START  LDA     TEMP-*

A leading asterisk is used to a indicate a 355sim control card; because of the asterisks, the following messages are generated:

*      PMC     ON
*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*
*<*>*<*>* ILLEGAL BCD CARD *<*>*<*>*
*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*

*      SYSTM
*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*
*<*>*<*>* ILLEGAL BCD CARD *<*>*<*>*
*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*

*      ORG     1024
*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*
*<*>*<*>* ILLEGAL BCD CARD *<*>*<*>*
*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*<>*<*>*<*>*<*>*<*>*<*>*<*>*<*>*

From the 355sim manual:

ILLEGAL BCD CARD
     This message indicates that an illegal * control card or patch card has been encountered. ...

Where did the asterisks come from?

There appears to be a problem in the GBCD conversion done by the GCOS daemon. The following job deck causes an error when submitted via the daemon but works fine with the 'gcos' command line program:

$ SNUMB HANOI $ IDENT CLAYTON,FOO $ OPTION ALGOL $ ALGOL LSTOU $ DATA S* 'BEGIN' 'INTEGER' N;

'PROCEDURE' HANOI(N,P1,P2,P3); 'INTEGER' N,P1,P2,P3; 'BEGIN'

'IF' N=0 'THEN' 'GOTO' EXIT; HANOI(N-1,P1,P3,P2); OUTPUT3(6,"/,"MOVE RING\,ZZD" FROM POLE\,ZD," TO POLE\, ZD\,N,P1,P3); HANOI(N-1,P2,P1,P3);

EXIT:

'END' OF PROCEDURE HANOI; N:=4; HANOI(N,1,2,3);

'END' OF ENTIRE PROGRAM $ EXECUTE $ ENDJOB

The error produced on the operator console is:

0944 gcos gcos_read_: Error converting card 13 to bcd: SNUMB = hanoi

It seems like it does not like the backslash maybe?

This is a very weird problem.

Oh GHM, in my home directory, attempting any I/O on certain file names will always crash, for example:

gtss, in >udd>Ring0>JJohnson:

GTSS 4JS3 (4.0)
*10 REM
*SAVE CRR03
DATA SAVED-CRR03
*SAVE CR03
DATA SAVED-CR03
*SAVE CR02

Error:  bad_area_format condition by gtss_mcfc_$open|1230
(>system_library_unbundled>bound_gcos_tss_)

CRR03 was fine, CR03 was fine, CR02 crashed.

new_proc, gtss again, trying to use these (existing) names as GTSS did create the CR02 file it crashed on:

*OLD CRR03
*OLD CR03
*OLD CR02

Error:  bad_area_format condition by gtss_mcfc_$open|1230
(>system_library_unbundled>bound_gcos_tss_)

Now, using a different directory:

new_proc
create_dir gtss
cwd gtss
gtss
GTSS 4JS3 (4.0)
*10 REM
*SAVE CRR03
DATA SAVED-CRR03
*SAVE CR03
DATA SAVED-CR03
*SAVE CR02
DATA SAVED-CR02
*OLD CRR03
*OLD CR03
*OLD CR02
*LIST

10 REM


*

As you can see above, the crash did not happen when using the new directory - it only happens in the home directory.

I have not investigated further.

Various issues prevent the GCOS daemon from working. Segments needing fixes are:

gcos_daemon_stat_.alm gcos_queue_job_.pl1 cv_bin_to_bcd_.pl1

It may be possible to not include the cv_bin_to_bcd_.pl1 fix if the simulator is changed to send the correct Hollerith code for the double-quote character (").

The GCOS daemon supports an "attach" command. It doesn't take any arguments and causes the "rdra" reader to be attached. It should accept an argument that allows specification of any available reader.

This appears to be a collision between formatting of >doc>privileged>map355.info and help command's expectations of proper format. Any info seg section title beginning "List of..." is expected to have an argument-like format, to permit the -brief operation of help to list those item names, and -ca XXX to list the description of item XXX.

In map355, we have:

      67  List of severity values:  The map355 command sets the following
      68  severity values to be returned by the severity active function when the
      69  "map355" keyword is used:
      70  
      71        Value     Meaning
      72  
      73          0       No error (or command not yet used)
      74          1       The assembly produced warning flags
      75          2       The objdk segment could not be created

help map355 -bf

Syntax as a command:  map355 pathname {-control_args}

Control arguments:   -check              -list, -ls
-argument list,      -comdk              -macro_file path
   -ag list          -gcos_list, -gcls   -noconvert

List of severity values:
"map355" keyword is used:
  the severity active function when the
\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\00
\c0\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000
\c\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\
\c000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\000\0
\c00\000\000\000\000\000\000