I have not personally used it, only read about it, but the RACF PWFALLBACK
option in a user's MFA segment is feature that might be quite helpful during
implementation/testing.
-Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of
https://en.wikipedia.org/wiki/Pascal_MicroEngine
In a message dated 7/16/2019 6:02:25 PM Central Standard Time,
bernd.oppol...@t-online.de writes:
and Pascal :-)
Pascal makes the same difference between := (assignment) and = (comparison)
So does C.
On Tue, 16 Jul 2019 22:36:43 +0200, Bernd Oppolzer wrote:
>>>
>>> I added BREAK, CONTINUE, RETURN, MODULE, LOCAL and STATIC;
>>> this was in the years from 2011 to 2016. No more need since.
>>>
>> I've done many of these as predefined quasi-identifiers, similar to Pascal's
>> predefined standard
Am 16.07.2019 um 22:16 schrieb Paul Gilmartin:
On Tue, 16 Jul 2019 21:37:38 +0200, Bernd Oppolzer wrote:
Am 16.07.2019 um 21:22 schrieb Seymour J Metz:
Furthermore: the more modern languages like Pascal, C and Java etc.
forbid the use of reserved symbols as variable names. This may be
On Tue, 16 Jul 2019 11:31:30 +0400 Jake Anderson
wrote:
:>Is there a utility or a program to verify if PDS is corrupted or not. To
:>provide me a statistical output whether if any of its control block is
:>corrupted or not .
IEBPTPCH PRINT TYPORG=PO
But you have to define your terms.
What are
On Tue, 16 Jul 2019 21:37:38 +0200, Bernd Oppolzer wrote:
>Am 16.07.2019 um 21:22 schrieb Seymour J Metz:
>>> Furthermore: the more modern languages like Pascal, C and Java etc.
>>> forbid the use of reserved symbols as variable names. This may be
>>> restrictive, but makes the compilers much
Am 16.07.2019 um 21:22 schrieb Seymour J Metz:
Furthermore: the more modern languages like Pascal, C and Java etc.
forbid the use of reserved symbols as variable names. This may be
restrictive, but makes the compilers much much simpler.
The cardinal sin in language design is to make the
> Furthermore: the more modern languages like Pascal, C and Java etc.
> forbid the use of reserved symbols as variable names. This may be
> restrictive, but makes the compilers much much simpler.
The cardinal sin in language design is to make the compiler simpler at the
expense of the user. An
Space is permitted almost everywhere in PL/1,
not in the middle of identifiers (in contrast to FORTRAN).
It is permitted before the left paranthesis of subscripts,
so there is no chance for the compiler to decide before
the semicolon or THEN in this case:
IF (possible index expr1) =
> Hmmm ... the only feature that Pascal lacks IMO is call-by-name,
Labels in Pascal are more like Fortran than Algol; strictly numeric. Prior to
the ISO standard, you didn't have conformant array parameters, which made Pasal
almost useless for handling arrays.
As to call by name, it's
Am 16.07.2019 um 20:40 schrieb Seymour J Metz:
Pascal makes the same difference between := (assignment) and = (comparison)
Pascal is a castrated version of Algol 60,
Hmmm ... the only feature that Pascal lacks IMO is call-by-name,
but this is something not easy to understand (and explain) to
> Pascal makes the same difference between := (assignment) and = (comparison)
Pascal is a castrated version of Algol 60,
> So does C.
You're missing Charles Mills's point; in C it is easy to type "=" where you
meant "=="; typing ":=" when you meant "=" is much less likely.
--
Shmuel
AFAIK a space is not permitted in PL/I between an identifier and the left
parenthesis for the subscripts. If that is correct then
IF (1) = (2);
can easily be recognized as an IF statement.
Id do, however, agree that it is very bad form to knowingly use a keyword as an
identifier.
--
and Pascal :-)
Pascal makes the same difference between := (assignment) and = (comparison)
So does C.
BTW: a free Pascal compiler for mainframe targets:
http://bernd-oppolzer.de/job9.htm
https://www.facebook.com/StanfordPascal
https://github.com/StanfordPascal/Pascal
unfortunately only AMODE 24
This double meaning of =, together with the absence of reserved words
makes PL/1 parsing extremely hard. Consider for example
IF (1) = (2);
now what does that mean?
Given a declaration
DCL IF (25) BIN FIXED (31);
that is, if IF is an array of integers, the "IF" statement above is a
valid
I generally code the variable on the left, but then I don't generally use
unsafe languages like C.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Discussion List on behalf of
Paul Gilmartin
One of the things that I liked about Algol was that "=" was always a comparison
operator; assignment was ":=". But even in PL/I that particular error is
impossible: the "=" in "IF foo=bar" can never be interpreted as assignment.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
For the first time ever, we are considering turning on SMS for tape. We've had
decades of business practice where SMS and tape never intersect. My main
concern is this: without SMS, a tape data set can be created and used without
involving any ICF catalog. One 'benefit' of this practice is that
Hi
I am running a clist which invokes TEST initially testing out an Assembler
program which calls a C program the C program has a call to __ceetest()
Seems nothing happens when the call is executed
First off I am wondering if the output of debug tool can have the same
destination i.e.
I work for a Bank and MFA was implemented several months ago. It was very
smooth for the most part.
One of the issues we ran into was our DR exercise, the MFA software did not
work on the DR recovered system since we usually do some SMS work in the first
IPL; we had to keep our "old" password
On Jul 16, 2019, at 9:40 AM, Mike Wawiorko
<014ab5cdfb21-dmarc-requ...@listserv.ua.edu> wrote:
>
> 1. as the TCP connection is made from a client to the tn3270 server (I
> assume you are not talking about OSA-ICC as that would have different issues)
>
> 2. or as an SNA sessions
Curtis,
Do you mean MFA:
1. as the TCP connection is made from a client to the tn3270 server (I
assume you are not talking about OSA-ICC as that would have different issues)
2. or as an SNA sessions are created to (selected) 3270 applications such
as TSO, CICS, IMS etc
Mike
The two main products that I'm aware of for MFA are IBM's MFA for RACF, and
Vanguard MFA. At $previoushjob I implemented the Vanguard product using RSA
SecurID as the MFA factor. Go on their websites and checkout which MFAs they
support.
Mark Jacobs
Sent from ProtonMail, Swiss-based
Our security folks want us to implement some form of two-factor authentication
for tn3270 access. (Currently, we just require users to be on campus or use our
VPN; the VPN uses DUO to provide two-factor authentication. But now they want
two-factor for on campus too.) Has anyone implemented
What is your definition of corrupted? Are you getting IO errors? Or some
other issue?
Sometimes a member will have PACK turned on and then functions outside of ISPF
cannot read it.
Lizette
> -Original Message-
> From: IBM Mainframe Discussion List On Behalf Of
> Jake Anderson
>
Get the PDS command from cbttape.org file 182. Free and it works great. The
latest can be found at http://cbttape.org/ftp/updates/CBT182.zip
PDS pds-dsname VER :
If you are trying to verify a PDSE then use the IEBPDSE - a free ISPF dialog to
drive it can be found here
CA-PDSMAN can o.a. analyze a PDS and produce statistics.
Kees.
> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of Jake Anderson
> Sent: 16 July, 2019 9:32
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: Verifying a PDS
>
> Hi Group
>
>
Hi Group
Is there a utility or a program to verify if PDS is corrupted or not. To
provide me a statistical output whether if any of its control block is
corrupted or not .
Jake.
--
For IBM-MAIN subscribe / signoff / archive
28 matches
Mail list logo
