Passwordrecords - Revision history

Admin at 04:55, 16 February 2026

2026-02-16T04:55:05Z

← Older revision		Revision as of 04:55, 16 February 2026
Line 2:		Line 2:
	[[bbs operation\|BBS Operation]] - <strong>Password Record Information</strong>		[[bbs operation\|BBS Operation]] - <strong>Password Record Information</strong>

	~~As you will notice if you use~~ the F6 Password Maintenance function, ~~there~~ is a ~~lot~~ of ~~information stored in~~ each ~~member's~~ password record. ~~The table below lists the field descriptions contained in the record:~~		When using the F6 Password Maintenance function, you will notice that each member record contains a substantial amount of stored information. Below is a description of each field contained within a password record.

	{\| class="wikitable		{\| class="wikitable"
	\|-		\|-
	\|+Password Record Field Descriptions		\|+Password Record Field Descriptions
Line 10:		Line 10:
	! Description		! Description
	\|-		\|-
	\| Access Level		\| Access Level
	\|Member's access level~~, which can range from 1 to 9~~. ~~See~~ the ~~"SETUP-~~Main ~~Parameters"~~ section ~~for a discussion of the default access level settings~~.		\|Member's access level (1–9). Default behaviors for each level are defined in the “SETUP – Main Parameters” section.
	\|-		\|-
	\|Membership ~~Experiation~~ Date		\| Membership Expiration Date
	\|If your ~~system is membership driven, then you may have certain membership periods. If you wish to have a user's membership expire on a certain date~~, ~~then~~ this ~~is the~~ field ~~you would set. Once~~ a ~~user's membership~~ expires, ~~their~~ level is ~~set~~ to the ~~"Member~~ expired ~~level"~~ in SETUP ~~(See "SETUP-Main Parameters")~~.		\|If your BBS uses time-based memberships, this field determines when a user’s access expires. When the date is reached, the user’s level is automatically changed to the “Member expired level” defined in SETUP.
	\|-		\|-
	\|Membership Name (Handle)		\| Membership Name (Handle)
	\|~~“Handle”~~ selected ~~by user. This field is limited~~ to 20 characters ~~and can contain any standard~~ ASCII ~~characters (~~Commodore graphics ~~are not allowed)~~. ~~Also, the membership name MUST~~ contain at least one alphabetic character, ~~because only~~ alphabetic characters ~~are matched during a membership name search~~.		\|The user’s selected handle (up to 20 characters). Standard ASCII only — no Commodore graphics. Must contain at least one alphabetic character, as searches match alphabetic characters only.
	\|-		\|-
	\|Password		\| Password
	\|~~User’s~~ password (~~entered by user~~)~~; 3-9 characters in length~~. Not case sensitive ~~and stored~~ as uppercase and numerals		\|User-defined password (3–9 characters). Not case-sensitive. Stored internally as uppercase letters and numerals.
	\|-		\|-
	\|Membership Information (DD$)		\| Membership Information (DD$)
	\|Not used by the system~~. Sysop may use at their discretion~~.		\|Reserved for SYSOP use. Not directly used by the system.
			This value is stored in the DD$ variable while the caller is online and may be displayed using the £a6 MCI command (if enabled).
	This ~~information~~ is stored in the ~~variable~~ DD$ while the caller is online and ~~can~~ be displayed ~~through~~ the £a6 MCI command (~~see section 3.8, on MCI commands~~)~~, but this MCI command can be disabled~~.
	\|-		\|-
	\|Blocks Uploaded		\| Blocks Uploaded
	\|~~Number~~ of blocks the ~~user has uploaded~~. This is a raw ~~figure~~ and does not ~~actually~~ represent ~~the user's~~ download credit.		\|Total number of blocks uploaded by the caller. This is a raw count and does not directly represent download credit.
	\|-		\|-
	\|Blocks Downloaded		\| Blocks Downloaded
	\|~~Number~~ of blocks ~~the user has~~ downloaded. ~~Download credit is a number depending on this figure, blocks downloaded,~~ and the ~~number of download credits~~ per upload ~~block (as defined~~ in ~~SETUP), so this can end up being a~~ negative ~~number~~.		\|Total number of blocks downloaded. Combined with uploads and the “credits per upload block” setting to determine download credit. This value can result in negative credit.
	\|-		\|-
	\|Time Remaining		\| Time Remaining
	\|~~Amount of time caller has~~ remaining for the ~~day~~. ~~This number is reset each night~~ to the ~~figures entered~~ in SETUP		\|Minutes remaining for the caller today. Reset nightly according to the limits defined in SETUP.
	\|-		\|-
	\|Number of Posts		\| Number of Posts
	\|Total number of public messages caller ~~has posted~~.		\|Total number of public messages posted by the caller.
	\|-		\|-
	\|Access Group		\| Access Group
	\|~~Defined~~ for future use.		\|Reserved for future use.
	\|-		\|-
	\|Last Date Called		\| Last Date Called
	\|~~Last~~ date ~~member logged on~~. Used during ~~the~~ midnight ~~routine to check~~ expiration and purge ~~dates~~.		\|Most recent login date. Used during midnight routines for expiration and purge checks.
	\|-		\|-
	\|Last Message Read		\| Last Message Read
	\|~~Last~~ public message the caller has read.		\|The last public message number the caller has read.
	\|-		\|-
	\|Real Name		\| Real Name
	\|User’s real name~~. Up~~ to 30 characters ~~in length~~.		\|User’s real name (up to 30 characters).
	\|-		\|-
	\|Phone Number		\| Phone Number
	\|User’s phone number~~. Up~~ to 15 characters ~~in length~~.		\|User’s phone number (up to 15 characters).
	\|-		\|-
	\|Birth Date		\| Birth Date
	\|User’s ~~birthdate~~		\|User’s birth date.
	\|-		\|-
	\|Email or ~~street address~~		\| Email or Street Address
	\|~~I find using~~ email ~~address more suited for the 2020s – no one wants to give up their~~ street address.		\|User’s contact information. Modern systems typically use email rather than street address.
	\|-		\|-
	\|City/State/Zip		\| City/State/Zip
	\|~~Self-Explanatory. Up~~ to 30 characters ~~in length~~.		\|User’s city, state, and zip code (up to 30 characters).
	\|-		\|-
	\|Block Size		\| Block Size
	\|~~Used to determine if caller~~ used ~~XModem or Punter on their most recent~~ file transfer. If 0~~, they used~~ XModem. If greater than ~~zero, they used~~ Punter ~~and the~~ value ~~shown is their~~ block size.		\|Indicates which protocol was used during the last file transfer.
			If 0 → XModem.
			If greater than 0 → Punter (value represents block size used).
	\|}		\|}

Admin at 21:26, 18 October 2025

2025-10-18T21:26:34Z

← Older revision		Revision as of 21:26, 18 October 2025
Line 1:		Line 1:
			{{DISPLAYTITLE:Password Records}}
	[[bbs operation\|BBS Operation]] - <strong>Password Record Information</strong>		[[bbs operation\|BBS Operation]] - <strong>Password Record Information</strong>

Admin at 03:13, 9 October 2025

2025-10-09T03:13:49Z

← Older revision		Revision as of 03:13, 9 October 2025
Line 65:		Line 65:
	\|Used to determine if caller used XModem or Punter on their most recent file transfer. If 0, they used XModem. If greater than zero, they used Punter and the value shown is their block size.		\|Used to determine if caller used XModem or Punter on their most recent file transfer. If 0, they used XModem. If greater than zero, they used Punter and the value shown is their block size.
	\|}		\|}

			Next Section: [[sysopstatus\|Sysop In/Out Flag]]

	[[bbs operation\|BBS Operation]]		[[bbs operation\|BBS Operation]]

Admin at 13:57, 4 October 2025

2025-10-04T13:57:16Z

← Older revision		Revision as of 13:57, 4 October 2025
Line 1:		Line 1:
	[[bbs operation\|BBS Operation]] <strong>Password ~~Maintenance~~</strong>		[[bbs operation\|BBS Operation]] - <strong>Password Record Information</strong>

	As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record:		As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record:

Admin at 13:56, 4 October 2025

2025-10-04T13:56:44Z

← Older revision		Revision as of 13:56, 4 October 2025
Line 1:		Line 1:
			[[bbs operation\|BBS Operation]] <strong>Password Maintenance</strong>

	As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record:		As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record:

Line 63:		Line 65:
	\|Used to determine if caller used XModem or Punter on their most recent file transfer. If 0, they used XModem. If greater than zero, they used Punter and the value shown is their block size.		\|Used to determine if caller used XModem or Punter on their most recent file transfer. If 0, they used XModem. If greater than zero, they used Punter and the value shown is their block size.
	\|}		\|}

			[[bbs operation\|BBS Operation]]

Admin: Protected "Passwordrecords" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2025-10-04T03:49:04Z

Protected "Passwordrecords" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 03:49, 4 October 2025
(No difference)

Admin: Created page with "As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record: {| class="wikitable |- |+Password Record Field Descriptions ! Field ! Description |- | Access Level |Member's access level, which can range from 1 to 9. See the "SETUP-Main Parameters" section for a discussion of the default access level settings. |- |Members..."

2025-10-04T03:48:57Z

Created page with "As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record: {| class="wikitable |- |+Password Record Field Descriptions ! Field ! Description |- | Access Level |Member's access level, which can range from 1 to 9. See the "SETUP-Main Parameters" section for a discussion of the default access level settings. |- |Members..."

New page

As you will notice if you use the F6 Password Maintenance function, there is a lot of information stored in each member's password record. The table below lists the field descriptions contained in the record:

{| class="wikitable
|-
|+Password Record Field Descriptions
! Field
! Description
|-
| Access Level
|Member's access level, which can range from 1 to 9. See the "SETUP-Main Parameters" section for a discussion of the default access level settings.
|-
|Membership Experiation Date
|If your system is membership driven, then you may have certain membership periods. If you wish to have a user's membership expire on a certain date, then this is the field you would set. Once a user's membership expires, their level is set to the "Member expired level" in SETUP (See "SETUP-Main Parameters").
|-
|Membership Name (Handle)
|“Handle” selected by user. This field is limited to 20 characters and can contain any standard ASCII characters (Commodore graphics are not allowed). Also, the membership name MUST contain at least one alphabetic character, because only alphabetic characters are matched during a membership name search.
|-
|Password
|User’s password (entered by user); 3-9 characters in length. Not case sensitive and stored as uppercase and numerals
|-
|Membership Information (DD$)
|Not used by the system. Sysop may use at their discretion.

This information is stored in the variable DD$ while the caller is online and can be displayed through the £a6 MCI command (see section 3.8, on MCI commands), but this MCI command can be disabled.
|-
|Blocks Uploaded
|Number of blocks the user has uploaded. This is a raw figure and does not actually represent the user's download credit.
|-
|Blocks Downloaded
|Number of blocks the user has downloaded. Download credit is a number depending on this figure, blocks downloaded, and the number of download credits per upload block (as defined in SETUP), so this can end up being a negative number.
|-
|Time Remaining
|Amount of time caller has remaining for the day. This number is reset each night to the figures entered in SETUP
|-
|Number of Posts
|Total number of public messages caller has posted.
|-
|Access Group
|Defined for future use.
|-
|Last Date Called
|Last date member logged on. Used during the midnight routine to check expiration and purge dates.
|-
|Last Message Read
|Last public message the caller has read.
|-
|Real Name
|User’s real name. Up to 30 characters in length.
|-
|Phone Number
|User’s phone number. Up to 15 characters in length.
|-
|Birth Date
|User’s birthdate
|-
|Email or street address
|I find using email address more suited for the 2020s – no one wants to give up their street address.
|-
|City/State/Zip
|Self-Explanatory. Up to 30 characters in length.
|-
|Block Size
|Used to determine if caller used XModem or Punter on their most recent file transfer. If 0, they used XModem. If greater than zero, they used Punter and the value shown is their block size.
|}