Re: BPCS Keyboard Mapping

Back in the day didn't BPCS like to tie "workstation data areas" to the
workstation id? And you wanted to keep your workstations the same for
your users like mine might be ROBS1, ROBS2 and so on. Using a generic
like QPADEV001, QPADEV002 that might be picked by a different user each
time they connected would mean your workstation data area might not be the
same.

Might have been more common in BPCS than in LX
See:
WRKOBJ BPCSUSRF/*ALL *DTAARA
and
SELECT SYSTEM_TABLE_SCHEMA, SYSTEM_TABLE_NAME, SYSTEM_TABLE_MEMBER
FROM QSYS2/SYSPARTITIONSTAT
WHERE system_table_schema='BPCSUSRF'
AND SYSTEM_TABLE_MEMBER NOT LIKE 'Z0%'
ORDER BY SYSTEM_TABLE_MEMBER

Ok, some of you will be freaked out by "QSYS2/SYSPARTITIONSTAT". It is
the one and the same physical object as QSYS2/SYSPSTAT. DSPFD on SYSPSTAT
will show you
Alternative file name
SYSPARTITIONSTAT
Basically there is a table on the i which automatically lists all members
on all tables. In fancy database talk a member is a partition. A
partitioned table is a file with members.
So if you don't have a decent sql tool to use and you have to use
Query/400 then use SYSPSTAT.

Rob Berendt